15:00:15 #startmeeting qa 15:00:15 Meeting started Tue Sep 17 15:00:15 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:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:15 The meeting name has been set to 'qa' 15:00:23 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours 15:00:47 o/ 15:01:51 o/ 15:02:20 #topic Announcement and Action Item (Optional) 15:02:37 Last week we released Tempest 40.0.0 15:02:39 #link https://review.opendev.org/c/openstack/releases/+/927833 15:04:04 that was an intermediary release, gmann do we want to set a deadline for releasing the final release for this cycle? 15:04:25 next week i'm around, but the week after that (the first week of October) i'm on vacation 15:05:53 as the cycle ends this month, we should release that between now and next week then, i'll to prep the patches 15:06:42 btw, TC and PTL elections end tomorrow: 15:06:44 #link #link https://governance.openstack.org/election/ 15:07:29 #topic Gate Status Checks 15:07:29 #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:07:43 nothing there 15:07:45 #topic Sub Teams highlights 15:07:45 Changes with Review-Priority == +1 15:07:45 #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:08:23 one patch currently blocked on nova-live-migration job that has been failing for couple of days 15:08:31 #link https://zuul.opendev.org/t/openstack/builds?job_name=nova-live-migration&project=openstack/tempest 15:09:15 does anyone know if there is gonna be a fix for that soon? if not, i'll make it non-voting so that we can land couple of patches that are currently blocked by that 15:10:02 #topic Periodic jobs Status Checks 15:10:03 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 15:10:03 Periodic stable slow: https://zuul.openstack.org/builds?job_name=tempest-slow-2024-1&job_name=tempest-slow-2023-2&job_name=tempest-slow-2023-1 15:10:04 Periodic extra tests: https://zuul.openstack.org/builds?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:10:06 Periodic master: https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic 15:11:50 looks good, only a few random not consistent failures 15:12:01 #topic Distros check 15:12:02 Centos 9: https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job_name=devstack-platform-centos-9-stream&skip=0 15:12:02 Debian: https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bookworm&skip=0 15:12:03 Rocky: https://zuul.openstack.org/builds?job_name=devstack-platform-rocky-blue-onyx 15:12:05 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:12:07 Noble: https://zuul.opendev.org/t/openstack/builds?job_name=devstack-platform-ubuntu-noble&skip=0 15:13:31 the periodic pipelines look quite stable 15:13:39 #topic Open Discussion 15:13:40 anything for the open discussion? 15:15:01 Nothing, from me 15:15:39 #topic Bug Triage 15:15:39 #link https://etherpad.openstack.org/p/qa-bug-triage-dalmatian 15:16:11 2 new bugs on devstack side, i havne't checked the details yet 15:17:07 I'd like to move openstack twoards running jobs with ansible 9 by default. The current default is 8. That said there is also the release going on so not moving terribly quickly 15:17:45 one thing we could do is to run some devstack jobs under ansible 9 either speculatively in unmerged changes or more permanently merging changes 15:18:03 any thoughts on the best way to do that as a sanity check with devstack + tempest? 15:18:53 maybe just propose a change that updates the base tempest job and then see what if anything breaks then we can decide if we want to proceed further from there? 15:19:29 well, yeah, as you said, propose the change and if everything behaves, we can merge, if not, we'll figure it out based on the failures 15:19:45 ok thanks 15:20:02 just make sure to wait until after the release before changing this globally 15:20:48 yes that is the case and why it hasn't changed yet 15:20:59 if we were earlier in the cycle we would be more adventurous 15:21:04 also nova-live-migration should be fixed rsn with the u-c bump for latest osc 15:22:04 ack, thanks 15:22:26 all right, anything else to bring up? 15:23:12 ok then, thanks everyone 15:23:17 #endmeeting