15:00:22 #startmeeting qa 15:00:22 Meeting started Tue Oct 29 15:00:22 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:22 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:22 The meeting name has been set to 'qa' 15:00:30 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours 15:00:41 \o 15:00:47 o/ 15:02:29 #topic Announcement and Action Items 15:02:44 there was the PTG last week 15:02:55 etherpad with the discussions: 15:03:13 #link https://etherpad.opendev.org/p/oct2024-ptg-os-qa 15:03:46 regarding the priority items, some were carried over from the previous cycle, some are new ( not a lot though) 15:03:48 #link https://etherpad.opendev.org/p/qa-epoxy-priority 15:04:31 i also sent a summary email to the ML earlier today 15:05:12 that's all news i have 15:05:29 let's get to business as usual 15:05:30 #topic Gate Status Checks 15:05:34 #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:05:48 no changes 15:05:51 #topic Sub Teams highlights 15:05:51 Changes with Review-Priority == +1 15:05:51 #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:06:57 there are 2 reviews, one depends on an unmerged change .. cannot be merged yet and the other is in the queue (there are couple of changes in devstack it depends on they seem to be in progress of merging already) 15:08:08 #topic Periodic jobs Status Checks 15:08:08 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:08:08 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:08:10 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:08:12 Periodic master: https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic 15:09:39 all green \o/ 15:09:47 #topic Distros check 15:09:47 Centos 9: https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job_name=devstack-platform-centos-9-stream&skip=0 15:09:47 Debian: https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bookworm&skip=0 15:09:49 Rocky: https://zuul.openstack.org/builds?job_name=devstack-platform-rocky-blue-onyx 15:09:51 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:09:53 Noble: https://zuul.opendev.org/t/openstack/builds?job_name=devstack-platform-ubuntu-noble&skip=0 15:10:26 all seem good enough, nice 15:11:37 #topic Open Discussion 15:11:37 anything for the open discussion? 15:12:17 do we want to switch the default nodeset to noble? iirc gmann was preparing this? 15:12:58 ah, that's a priority item 15:13:22 what's next after new tempest tag created? to clear stable branches after py3.8 constraints drop? 15:13:56 https://review.opendev.org/c/openstack/requirements/+/925201 15:15:17 frickler: yep, right now it's in testing phase until the end of the month .. hopefully by then we'll sort our all problems and then we can fully migrate 15:15:41 ykarel: hmm, my understanding is that we don't have to drop it from the stable branches .. let me find one email 15:16:41 looking at https://review.opendev.org/q/topic:%22migrate-to-noble%22 looks like enough work to keep us busy until the end of the year at least :-( 15:17:03 oh, i can't find the link , gmann sent the info about py3.8 to the ML under "[all[qa] Tempest dropping python 3.8 support" 15:17:40 https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/FOWV4UQZTH4DPDA67QDEROAESYU5Z3LE/ 15:18:01 that, thanks frickler 15:18:12 (Archived-At header in the mail, very useful) 15:19:25 kopecmartin, yeap i saw that but not clear on next steps to clear 15:19:43 stable branches are kind of blocked to merge patches currently 15:21:08 oh, i see, i'm getting up to speed, hmm, one sec 15:21:42 o/ 15:23:22 too see i get it right, stable branches use py38 and master tempest? 15:23:41 yes currently 15:25:21 https://github.com/openstack/devstack/blob/stable/2023.1/stackrc#L301-L304 15:26:05 until xena https://github.com/openstack/devstack/blob/unmaintained/xena/stackrc#L305-L308 15:27:38 if i get the email right, we should use tempest 41, not master .. i need to take a closer a look 15:27:45 do you have a link to a job that currently fails? 15:28:22 https://zuul.openstack.org/builds?project=openstack%2Fneutron&pipeline=periodic-weekly&skip=0 15:28:49 but it is only 2023.1 that is affected, right? and that branch is going eom next week 15:29:07 frickler, xena to 2023.1 are atleast impacted 15:29:26 https://github.com/openstack/devstack/commit/788593a9104bee6b85ecfd157c2e7c327c76c647 was done in past for wallaby, seems same needs to be done for all these branches too 15:31:13 well for eom branches failing test jobs can simply be dropped. but also from my upstream pov, they don't exist at all 15:31:51 but most of the jobs failing :) and fix looks straightforward 15:32:33 stable/2023.1 about to go eom and with these failures we can't merge open patches there 15:34:20 * ykarel need to drop 15:34:42 ykarel is right, the tempest branch should be overriden in the stable branches 15:34:47 let's confirm with gmann 15:37:04 all right, let's continue this discussion later today when gmann is around and confirm the plan for the stable branches 15:37:15 anything else for the open discussion? 15:38:05 ok, thanks everyone, see you online 15:38:05 #endmeeting