15:00:52 #startmeeting qa 15:00:52 Meeting started Tue Sep 13 15:00:52 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:53 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:53 The meeting name has been set to 'qa' 15:01:02 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours 15:01:03 agenda ^ 15:01:54 o/ 15:02:07 hmm, i messed it up, i started the meeting in a different channel too, now i wonder what will happen :D 15:02:16 just 2 weeks on pto and i forget everything :D 15:02:57 kopecmartin: I think those will be independent, just end the other one 15:03:04 i did 15:03:17 o/ 15:03:30 and i can see a new file already - https://meetings.opendev.org/meetings/qa/2022/ 15:03:41 i wonder whether this meeting will override that once it's ended 15:03:53 let's test that, we'll see 15:04:02 o/ 15:04:34 o/ 15:05:46 anyway, i'm back, long time no see, let's see how many things i've missed 15:05:51 #topic Announcement and Action Item (Optional) 15:06:16 we have a new PTL, congrats kopecmartin :) 15:06:30 thanks 15:06:51 congrats! 15:07:04 interesting fact, i was actually in the Antelope canyon while the nomination process for Antelope cycle was in progress 15:07:24 :D 15:07:33 that's dedicated preparation, great effort 15:07:56 :D 15:08:11 was anyone else interested in the PTL role? 15:08:29 i wasn't following any communication, i only made that one patch to nominate myself 15:09:10 I don't think so, I would have suggested to move to distributed otherwise 15:09:22 but of course, i'm happy to continue serving as PTL .. i was just curious 15:09:26 ok, thanks 15:10:14 the whole timing was weird, announcing things very late and changing dates on the fly 15:11:02 yeah, that was a bit weird, usually these things are announced much sooner , but luckily everything ended up great 15:11:58 the other thing to announce is a tempest release - a new tag - we need to do that soon 15:12:55 #topic Zed Priority Items progress 15:12:57 #link https://etherpad.opendev.org/p/qa-zed-priority 15:13:00 any updates on this front? 15:13:45 I think we should be in feature freeze now? so not much room for progress any more 15:15:29 that's true, any outstanding items will be triaged and discussed during PTG and some we'll carry over to the next cycle then 15:15:57 #topic OpenStack Events Updates and Planning 15:16:03 #link https://etherpad.opendev.org/p/qa-antelope-ptg 15:16:13 if you have anything you would like to discuss during the ptg, please feel free to add it to the etherpad ^^ 15:16:34 we have less than a month until the event 15:16:47 ~ a month 15:18:04 hm, this reminds me, we should create a doodle so that we can find an appropriate time slot for the sessions 15:18:39 there's a free alternative to doodle, but I need to look for the link 15:19:22 sounds good, let me know then and we can use that instead 15:19:42 https://framadate.org/abc/en/ 15:20:55 it looks interesting, i'll check it out, thanks 15:21:18 #topic Gate Status Checks 15:21: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:21:36 no reviews there 15:21:37 anything urgent for review? 15:22:08 I've just remove -1 from this patch. https://review.opendev.org/c/openstack/tempest/+/821732 . 15:22:26 It is stuck for long time now I think. 15:23:02 yeah, still on my review list 15:23:02 cant 15:23:07 can't get my head around taht 15:23:15 But I think we won't go with it now as we are in the feature freeze? 15:24:12 It just makes sure that some tests run in serial mode and uses locks to ensure it. But I do not know much about it too. 15:25:14 it depends, let's see, but if we decide to move that forward we'll do it not later than at the beginning of the next cycle 15:25:37 ack 15:25:41 #topic Bare rechecks 15:25:47 #link https://etherpad.opendev.org/p/recheck-weekly-summary 15:26:02 we're at zero although only out of 2 rechecks .. 15:26:09 but still good news 15:26:37 #topic Periodic jobs Status Checks 15:26:46 stable 15:26:46 #link #link https://zuul.openstack.org/builds?job_name=tempest-full-yoga&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:26:53 master 15:26:54 #link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic 15:27:32 fips job timeouted today and tempest-full-oslo-master failed 15:27:48 but maybe it's just a random thing? we'll see tomorrow 15:28:48 #topic Distros check 15:28:55 cs-9 15:28:55 #link https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job_name=devstack-platform-centos-9-stream&skip=0 15:29:01 fedora 15:29:01 #link https://zuul.openstack.org/builds?job_name=devstack-platform-fedora-latest&skip=0 15:29:08 debian 15:29:08 #link https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bullseye&skip=0 15:29:14 jammy 15:29:15 #link https://zuul.openstack.org/builds?job_name=devstack-platform-ubuntu-jammy&job_name=devstack-platform-ubuntu-jammy-ovn-source&job_name=devstack-platform-ubuntu-jammy-ovs&skip=0 15:29:32 all good, passing last few days but fedora which has been failing ;/ 15:29:58 although just on stable branches 15:30:02 master seems ok 15:30:07 fedora needs updating to f36, not sure when ianw will have time 15:30:14 or maybe someone else 15:30:55 and then I think we can drop those from stable branches 15:31:10 they never have been working for very long 15:32:52 ah, that reminds me of another PTG topic. decide which jammy variant to make standard 15:33:06 true, i don't see any passing builds on stable branches and i already scrolled to February 15:33:13 * frickler goes etherpadding 15:33:18 +1 15:34:09 #topic Sub Teams highlights 15:34:15 Changes with Review-Priority == +1 15:34:20 #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:34:38 nothing there 15:34:55 any reviews needing attention? 15:35:25 Nothing from my side 15:36:02 #topic Open Discussion 15:36:07 anything for the open discussion? 15:36:23 any plans for rockylinux? 15:36:47 now I remember, there was another patch proposed while you were away 15:36:50 I think I saw a patch for that 15:36:52 ya 15:37:25 really? that'd be great, i came to a dead end :/ 15:37:45 well, mostly ran out of time 15:37:46 https://review.opendev.org/c/openstack/devstack/+/855393 15:37:58 looks pretty easy compared to what you did 15:38:02 I was going to mention the slow ansible loops problem we've run into in a couple of places. The way ansible runs tasks each loop iteration is like a new task which includes all the task overhead. This can take 2-6 seconds in a lot of cases. This cost becomes a problem when you run a loop against a large list of inputs. 15:38:40 Please be on the lookout for these problems as addressing them can add nice easy speedups to jobs. Also, you can avoid copying one file at a time for example and use synchronize to do it with one task for example 15:39:31 frickler: it does, i wonder what i did wrong :D 15:39:50 clarkb: thanks for the heads up, i'll check some of my jobs wether we do something like that there or not 15:43:02 i'll check the rocky patch later, but it looks really good 15:43:12 #topic Bug Triage 15:43:18 #link https://etherpad.openstack.org/p/qa-bug-triage-zed 15:43:28 numbers are recorded ^^ 15:43:46 this is all from my side for today, anything else to discuss? 15:45:23 thanks everyone 15:45:24 #endmeeting