15:00:34 #startmeeting qa 15:00:34 Meeting started Tue Dec 10 15:00:34 2024 UTC and is due to finish in 60 minutes. The chair is kopecmartin. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:34 The meeting name has been set to 'qa' 15:00:41 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours 15:00:48 agenda ^ 15:00:57 o/ 15:02:20 \o 15:02:30 o/ 15:02:41 Nathan proposed openstack/tempest master: Fixed encryption type methods to comply with documentation https://review.opendev.org/c/openstack/tempest/+/935526 15:02:52 hey gmann isn't it too early for you? 15:03:00 o/ 15:03:21 kopecmartin: I am attending board meeting today so can join here too :) 15:03:26 :) 15:03:38 #topic Announcements and Action Items 15:04:04 this is the last office hour before the holidays which means the last office hour this year 15:04:38 o/ 15:04:39 as I mentioned last time, i won't be able to host these in the new year, so we'll need a new volunteer :) 15:04:44 hi nperez 15:05:23 one of the discussed options was that gmann would take over, however, in that case we'd shift the meeting for a later time to better accomodate his time zone 15:05:49 if that happens, it'll be shared on the ML as well 15:07:44 oh, one other update, i've got a volunteer for reviews (as my capacity for this kind of thing in the new year will be decreased) 15:08:06 tosky volunteered that he would like to help with reviews on tempest side 15:08:54 you may have seen his commits to cinder-tempest-plugin and a few related projects, e.g. cinder, glance and even tempest 15:09:17 even though I don't know a lot of the internal bits, so I may not always be perfectly helpful 15:09:44 (I do have some experience on devstack and grenade, though, to be refreshed a bit) 15:10:07 that is absolutely ok .. i'm sure tempest can benefit from that 15:10:08 cool, yes, I remember you were around when I started digging into devstack 15:10:19 perfect thanks tosky 15:10:32 luigi is everywhere ;) 15:10:33 https://review.opendev.org/q/from:ltoscano@redhat.com 15:12:12 #action so, one action item for me is to hand over the hosting of this office hour and find (if needed) a new time 15:13:01 that's all from announcements 15:13:26 #topic Epoxy Priority Items progress 15:13:26 #link https://etherpad.opendev.org/p/qa-epoxy-priority 15:13:33 * kopecmartin checking if there are any updates 15:14:00 * kopecmartin feeling a bit ashamed as he didn't get to a few action items there :/ 15:15:16 the migration to noble went more or less fine 15:15:20 the email thread: 15:15:21 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/JOMDY26TCW7OX3NXRGOYQCIDXNNJ4E25/ 15:15:50 well still some cleanup happening, but nothing major that I'm aware of, yes 15:15:56 one of the bug is in devstack-plugin-container CRI-O installation on noble failing 15:16:12 only 24 patches left open out of almost a hundred 15:16:14 #link https://review.opendev.org/q/topic:%22migrate-to-noble%22+status:open 15:16:17 I pinged hongbin who is mainly maintaining this plugin and he will look into that 15:16:23 great 15:16:40 yeah, I am trying to get those merged but they may take time 15:17:08 CRI-O thing only impact k8s jobs 15:18:03 and the doc job migration is still left 15:18:56 ack , thanks 15:19:22 let's move on 15:19:24 #topic Gate Status Checks 15:19:24 #link https://review.opendev.org/q/label:Review-Priority%253D%252B2+status:open+(project:openstack/tempest+OR+project:openstack/patrole+OR+project:openstack/devstack+OR+project:openstack/grenade) 15:19:35 2 patches, both approved 15:19:50 #topic Sub Teams highlights 15:19:50 Changes with Review-Priority == +1 15:19:50 #link https://review.opendev.org/q/label:Review-Priority%253D%252B1+status:open+(project:openstack/tempest+OR+project:openstack/patrole+OR+project:openstack/devstack+OR+project:openstack/grenade) 15:20:06 6 patches, most of them approved 15:20:30 i need a second opinion on 15:20:32 #link https://review.opendev.org/c/openstack/tempest/+/933308 15:20:36 and 15:20:37 #link https://review.opendev.org/c/openstack/tempest/+/935526 15:21:09 hey you wanted me to fix the "closes bug" part of my commit message and fixed it 15:21:27 perfect, thank you 15:21:50 https://review.opendev.org/c/openstack/tempest/+/935526 15:21:55 thank you for reviewing it 15:22:33 thank you for working on it 15:23:23 i reviewed it, let's see what the automatic jobs think 15:23:48 #topic Periodic jobs Status Checks 15:23:48 Periodic stable full: https://zuul.openstack.org/builds?pipeline=periodic-stable&job_name=tempest-full-2023-1&job_name=tempest-full-2023-2&job_name=tempest-full-2024-1&job_name=tempest-full-2024-2 15:23:48 Periodic stable slow: https://zuul.openstack.org/builds?job_name=tempest-slow-2024-2&job_name=tempest-slow-2024-1&job_name=tempest-slow-2023-2&job_name=tempest-slow-2023-1 15:23:50 Periodic extra tests: https://zuul.openstack.org/builds?job_name=tempest-full-2024-2-extra-tests&job_name=tempest-full-2024-1-extra-tests&job_name=tempest-full-2023-2-extra-tests&job_name=tempest-full-2023-1-extra-tests 15:23:52 Periodic master: https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic 15:24:36 you can drop 2023.1 from those searches now 15:24:44 that moved to unmaintained 15:24:47 oh, right, thanks frickler 15:26:15 all builds looks pretty standard 15:27:04 #topic Distros check 15:27:04 Centos 9: https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job_name=devstack-platform-centos-9-stream&skip=0 15:27:04 Debian: https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bookworm&skip=0 15:27:06 Rocky: https://zuul.openstack.org/builds?job_name=devstack-platform-rocky-blue-onyx 15:27:08 Jammy: https://zuul.opendev.org/t/openstack/builds?job_name=devstack-platform-ubuntu-jammy-ovn-source&job_name=devstack-platform-ubuntu-jammy-ovs&skip=0 15:27:10 Noble: https://zuul.opendev.org/t/openstack/builds?job_name=devstack-platform-ubuntu-noble&skip=0 15:27:59 the latter two also need updates now I think. more noble less jammy 15:29:05 oh, right 15:29:53 hmm, the search filters based on the name only 15:30:14 .. on the other hand, it might be good to see the results on the unmaintained branch 15:30:24 hmm, but if there is something wrong, we can't fix that anyway 15:30:36 I'll try to limit the search 15:30:40 yes, but devstack-platform-ubuntu-jammy-ovn-source was replaced by devstack-platform-ubuntu-noble-ovn-source for example on master 15:31:32 right .. ok, another action item then 15:31:34 and devstack-platform-ubuntu-noble is replaced by tempest-full-py3 ;) 15:31:43 #action kopecmartin to update the above searches 15:32:00 instead there is devstack-platform-ubuntu-jammy now. or so I think 15:33:27 anyway, we can go on I think 15:33:52 ack 15:33:54 #topic Open Discussion 15:33:54 anything for the open discussion? 15:34:14 I wanted to call out https://bugs.launchpad.net/devstack/+bug/2082617 and less the specific issue and more the thing that made it difficult to debug 15:34:50 as noted in there I think the |default(omit) default module arguments may mask early detection of failures to render the config dicts 15:35:22 it would probably be a good idea for the qa team to investigate refactoring that in devstack so that we're less likely to pass a null default and wonder why the job isn't working as expected 15:36:13 The good news is I don't think jobs would pass if they have broken jinja in their localrc config so I don't think we have a bunch of jobs doing the wrong thing 15:36:19 but debugging is difficult as is 15:37:58 that's a good point 15:38:16 ah, yes, that was a fancy issue. I just think the "qa team" is essentially near zero by now, so not sure who would take that up. except tosky maybe? :) 15:39:40 i'll check it 15:39:56 ya its an easy one to fix at a superficial level. Just update that CEPH ip address to the private ipv4 address and move on. My concern is more that debugging future issues may be more painful/ less obvious 15:40:14 and I suspect changing how defaults are handled may expose the issue more directly with a "jinja broke" error 15:41:29 right, that;s a good idea 15:42:06 cool, anything else/ 15:42:08 ? 15:43:42 ok then, we're done 15:43:46 thank you all 15:43:52 see you around 15:44:01 o/ 15:44:04 #endmeeting