15:00:19 #startmeeting qa 15:00:19 Meeting started Tue Aug 23 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:28 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours 15:00:29 agenda ^^ 15:00:36 o/ 15:00:52 o/ 15:01:19 \o 15:01:47 o/ 15:04:26 \o 15:04:27 let's start 15:04:28 #topic Announcement and Action Item (Optional) 15:05:17 i'm gonna be on PTO for 2 weeks 15:05:20 starting this Friday 15:05:31 August 26th - September 9th 15:05:35 just FYI 15:05:43 ack 15:06:11 do we want to cancel the office hours? or is anyone interested in hosting them? 15:07:10 I could chair, but not sure who would join 15:07:21 I can do for 30, but might not be available for 6 15:07:39 but nothing specific on agenda from me so I am ok to cancel too 15:07:39 maybe just give it a try, will see who turns up 15:07:48 yeah, that also work 15:08:03 it's ok just to start the meeting, in case someone from the community needed to raise something 15:08:15 and maybe check jobs 15:08:23 that's a good idea, too, ack 15:08:35 thanks frickler 15:09:44 moving on 15:09:46 #topic Zed Priority Items progress 15:09:52 #link https://etherpad.opendev.org/p/qa-zed-priority 15:09:56 anything new here? 15:10:29 nothing from me 15:10:42 i've been working on the os_admin for manager 15:11:04 i took the approach that gmann told me 15:11:06 and addes in the methods the client option 15:11:17 then, next step would be check which tests call the manager, and pass the client 15:11:30 the behavior right now remains the same, still using os_admin clients as default 15:11:40 and then change per test 15:12:26 #link https://review.opendev.org/c/openstack/tempest/+/852377 15:12:33 sounds good 15:14:10 * kopecmartin checking the etherpad 15:14:39 i don't have any updates too, i was working on the rocky job for a bit but i've been failing to get back to that for some time now 15:15:11 #topic OpenStack Events Updates and Planning 15:15:17 #link https://etherpad.opendev.org/p/qa-antelope-ptg 15:15:24 if you have anything you would like to discuss during the ptg, please feel free to add it to the etherpad ^^ 15:15:51 kopecmartin: did we sign up for PTG? 15:16:00 yes 15:16:06 cool, +1 15:16:15 i've filled the team signup a week or 2 ago 15:16:21 we should be on track 15:16:40 the date should be -21 iiuc, the friday was added again 15:17:06 yeah 26 is deadline 15:17:47 should we be discussing time slots alraedy? 15:18:01 or will it be enough if i create the doodle in 2 weeks? 15:18:11 kopecmartin: that will be done after the 26 on ptg bot directly 15:18:31 i think we can start doodle or collecting data 15:18:58 but checking conflicts with other team is important which we will get to know after 26 only when team start the slot booking in ptg bot 15:19:02 I would rather do it later and schedule around other teams if possible 15:19:07 yeah 15:19:16 sounds good 15:20:22 #topic Gate Status Checks 15:20:26 #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:20:45 no reviews there 15:20:46 anything urgent for review? 15:21:55 #topic Bare rechecks 15:22:00 #link https://etherpad.opendev.org/p/recheck-weekly-summary 15:22:05 #info STOP DOING BARE RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures 15:22:20 just to keep that fresh in mind :) 15:22:40 last week i did a bare recheck, shame on me :D 15:22:53 muscle memory without thinking .. 15:23:02 you get two weeks off to ponder that ;-P 15:23:21 :D 15:23:39 #topic Periodic jobs Status Checks 15:23:45 stable 15:23:45 #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:23:53 master #link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic 15:24:01 all seems ok 15:24:06 \o 15:24:17 #topic Distros check 15:24:23 cs-9 15:24:23 #link https://zuul.openstack.org/builds?job_name=tempest-full-centos-9-stream&job_name=devstack-platform-centos-9-stream&skip=0 15:24:29 fedora 15:24:29 #link https://zuul.openstack.org/builds?job_name=devstack-platform-fedora-latest&skip=0 15:24:34 debian 15:24:35 #link https://zuul.openstack.org/builds?job_name=devstack-platform-debian-bullseye&skip=0 15:24:40 jammy 15:24:41 #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:25:33 we've seen better 15:25:51 seems like something got broken in fedora 15:26:18 and centos is on a rollercoaster again 15:27:59 i don't see anything specific there, i'll check the logs after the meeting more closely 15:28:15 #topic Sub Teams highlights 15:28:18 Changes with Review-Priority == +1 15:28:26 #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:28:57 we have several devstack reviews there 15:29:18 I added some there, mostly small cleanups I found while doing a test deployment 15:29:46 frickler: thanks for voting here, i was a bit confused with this file - https://review.opendev.org/c/openstack/devstack/+/853326/2/functions 15:29:54 the rest is ok for sure, i'll review too 15:30:17 Yes, thank you for the reviews there! 15:31:01 eliadcohen: and thank you for contributing ;) 15:31:18 Pleasure :) Looking forward to do more 15:31:53 perfect, that's what we want to always hear 15:32:13 #topic Open Discussion 15:32:18 anything for the open discussion? 15:32:49 I have one other thing that I noticed where I don't have a solution yet 15:33:13 in cleanup.sh, we do something like "sudo pkill -f foobar" 15:33:27 which instantly also kills the sudo command itself 15:33:53 which in turn leads to output getting scrambled and needing a "stty sane" to restore after finishing 15:34:09 the latter is how I actually noticed this 15:35:12 the clumsy approach would be "pgrep foobar | xargs sudo kill" but maybe there is a better idea 15:35:42 is it expected behaviour of kill? 15:36:00 logically i don't see a reason why kill should also kill sudo, it's interesting 15:36:12 pkill kills any process which has "foobar" in its command line 15:36:34 except itself, but the sudo is another process 15:37:01 maybe I'll just write a bug report if there isn't a spontaneous idea 15:37:59 unfortunately i don't have anything :/ 15:40:10 o.k, I'll go with the bug then 15:40:46 there is one topic i wanted to raise -> S-RBAC 15:40:55 so , what's our game plan in QA? 15:41:07 i started with tempest -> https://review.opendev.org/c/openstack/tempest/+/847760 15:41:44 gmann: would you say that our goal now should be make the tests passsing in that job ^^ ? 15:42:06 I did not get time on this but will try to work on it next week or so. working on nova side currently 15:42:32 will check that 15:42:53 yeah, np, right now i'm just curious what are our milestones, smaller goals 15:43:10 so that i know what to focus on, finding some help with the patches and etc .. 15:43:12 thanks 15:44:51 #topic Bug Triage 15:44:56 #link https://etherpad.openstack.org/p/qa-bug-triage-zed 15:45:08 numbers recorded 15:45:33 unfortunately i haven't done much triaging lately 15:45:41 this is all from my side for today, anything else to discuss? 15:47:08 thanks everyone 15:47:10 #endmeeting