15:00:19 #startmeeting qa 15:00:19 Meeting started Tue Feb 22 15:00:19 2022 UTC and is due to finish in 60 minutes. The chair is kopecmartin. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:19 The meeting name has been set to 'qa' 15:00:27 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Weekly_QA_Team_meeting 15:00:30 agenda ^^^ 15:03:19 o/ 15:03:51 hi gmann 15:03:56 kopecmartin: hi 15:04:52 i'm just creating the doodle to find a time slot for qa session for PTG 15:05:05 i've created an etherpad for the topics 15:05:11 cool, link? 15:05:15 #link https://etherpad.opendev.org/p/qa-zed-ptg 15:06:03 when is deadline to book slot in PTG? 15:06:48 March 11th 15:07:24 #link http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027051.html 15:08:03 ok, I will also get TC one started but those will be mostly during end of PTG week 15:08:26 any suggestion towards what days should I target the doodle? 15:08:42 do we want 2 2-hour slots like last time and the time before? 15:09:11 one 2-hour slot one day, the other another day 15:10:13 yeah, I think same as previous like during start of the PTG. I will schedule the TC+PTL sessions on Monday or so. 15:10:35 +1 on 2 2 hrs slot 15:11:15 ack 15:12:16 i'm just filling the team sign up form .. what groups do we need to avoid schedule conflicts with? 15:12:18 TC 15:12:44 works for me 15:14:53 great 15:14:57 * kopecmartin creating the doodle 15:15:04 well I would like to avoid kolla if possible 15:15:27 ack 15:20:15 #link https://doodle.com/poll/q5yzatzh45brt5v2 15:20:18 gmann: frickler ^^ 15:20:40 kopecmartin: thanks 15:21:48 it should be in UTC timezone 15:24:18 good, this was PTG, what do we have next 15:24:26 #topic Yoga Priority Items progress 15:24:30 #link https://etherpad.opendev.org/p/qa-yoga-priority 15:24:34 any updates? 15:25:36 nothing specific from me. 15:26:00 me neither :/ 15:26:11 #topic Gate Status Checks 15:26:16 #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+OR+project:openstack/hacking) 15:26:47 no changes there 15:27:02 #topic Periodic jobs Status Checks 15:27:10 #link https://zuul.openstack.org/builds?job_name=tempest-full-xena&job_name=tempest-full-wallaby-py3&job_name=tempest-full-victoria-py3&job_name=tempest-full-ussuri-py3&pipeline=periodic-stable 15:27:17 #link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic 15:27:42 tempest-full-xena job failed, but it looks like a random issue 15:28:12 c9s is still broken 15:28:58 gmann: do you know the status in nova? 15:29:04 yeah, we discussed it in nova meeting. and need to get the tempest series in for solve that, I will work on that next week. 15:29:40 ah, that was the thing with waiting until the guest has finished booting 15:29:44 yeah 15:30:11 did not get chance to do that due to feature freeze things 15:30:53 good , thanks 15:30:58 I wonder if there would be a different solution, since it may also happen in the real world that someone tries to detach a volume right after creating an instance or rebooting it 15:31:17 but maybe a topic for nova rather than here 15:31:49 is there a bug or gerrit topic for that? just so that i can keep track of that 15:32:22 yeah we have bug for that 15:33:02 #link https://bugs.launchpad.net/nova/+bug/1960346 15:33:16 thanks 15:34:34 #topic Sub Teams highlights 15:34:38 Changes with Review-Priority == +1 15:34:44 #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+OR+project:openstack/hacking) 15:35:04 i see 2 reviews, one approved, the other one is 15:35:07 #link 15:35:10 #link https://review.opendev.org/c/openstack/devstack/+/828877 15:35:46 related to neutron, there are +1 from the team already 15:38:29 it has my +2, too, though I'm still worried about how fragile the OVN setup seems 15:40:10 yeah .. seems ok, the check jobs passed, in the review and in a testing one as well (https://review.opendev.org/c/openstack/devstack/+/828895/) 15:40:16 so hopefully we should be ok 15:43:56 #topic Open Discussion 15:43:59 anything for the open discussion? 15:44:29 #link https://review.opendev.org/c/openstack/governance/+/830454 15:44:34 zed runtimes 15:45:01 I'd really like to see py3.10 in there, but not sure if Jammy will be on time 15:45:28 and they didn't manage to switch the default from 3.9 yet 15:46:13 yeah, it is supposed to be released in april which is after Zed cycle satrt 15:46:13 maybe we could run unit tests at least on f35? 15:46:44 but we can have non voting py3.10 which is already a WIP patch 15:47:33 non voting py3.10 for unit tests sounds great 15:47:57 #link https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/821863 15:49:10 good 15:49:33 yeah, focal still hasn't python3.10, though 15:49:38 yeah 15:50:07 I'll ask in opendev whether we'd be willing to run that on f35 15:50:07 I will add this topic in TC PTG also and if we have Jammy releasing nearby Zed starting then we can think of 15:50:19 sure. 15:50:36 +1 15:51:36 anything else to discuss? 15:52:47 #topic Bug Triage 15:52:52 #link https://etherpad.opendev.org/p/qa-bug-triage-yoga 15:52:57 bug numbers are recorded at ^ 15:53:44 i don't have any specific bug to bring up 15:53:49 so that's it 15:54:14 please mark your availability for QA PTG doodle linked above and see you around 15:54:15 thanks 15:54:28 sure, thanks 15:54:33 #endmeeting