15:01:46 #startmeeting qa 15:01:46 Meeting started Tue Dec 14 15:01:46 2021 UTC and is due to finish in 60 minutes. The chair is kopecmartin. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:46 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:46 The meeting name has been set to 'qa' 15:01:53 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Weekly_QA_Team_meeting 15:01:58 agenda ^^ 15:02:29 o/ 15:03:46 hey o/ 15:03:59 hi o/ 15:04:02 let's start by going through the usual 15:04:26 #topic Announcement and Action Item (Optional) 15:04:39 nothing specific from me here 15:04:42 o/ 15:04:44 #topic Yoga Priority Items progress 15:04:51 #link https://etherpad.opendev.org/p/qa-yoga-priority 15:05:02 any updates on the priority items? 15:05:03 hello 15:05:21 hey lpiwowar, gmann, soniya29 o/ 15:06:35 o/ 15:06:49 no updates from my side w.r.t priority items 15:06:59 same with me 15:07:09 we just should proceed with the fips patches, but let's talk about that in a minute 15:08:00 gmann: anything for "Migration of Devstack and Tempest tests to new secure RBAC"? anything i can help with? 15:08:18 kopecmartin: not yet, few things under work but not up as such 15:08:38 ok, thanks 15:09:06 soniya29: what about "Cleanup of duplicated scenario.manager"? any blockers i could help with? 15:10:17 kopecmartin, i haven't started with it yet :) 15:10:43 soniya29: np, just let me know if i can help you in any way :) 15:10:51 kopecmartin, yeah, sure 15:11:01 sure, moving on 15:11:01 #topic OpenStack Events Updates and Planning 15:11:07 nothing here, let's skip 15:11:11 #topic Gate Status Checks 15:11: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:11:20 no changes with priority == +2 15:12:06 #topic Periodic jobs Status Checks 15:12:11 #link https://zuul.openstack.org/builds?job_name=tempest-full-xena-py3&job_name=tempest-full-wallaby-py3&job_name=tempest-full-victoria-py3&job_name=tempest-full-ussuri-py3&job_name=tempest-full-train-py3&pipeline=periodic-stable 15:12:18 #link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic 15:12:26 all green \o/ 15:12:35 any gate issues to bring up? 15:13:02 nothing I have seen 15:13:20 the was a pypi hickup earlier today 15:13:28 should be fixed by now 15:13:48 oh, perfect 15:14:18 #topic Sub Teams highlights 15:14:22 Changes with Review-Priority == +1 15:14: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+OR+project:openstack/hacking) 15:14:39 no changes there 15:14:45 any change to bring up? 15:15:36 i have this one regarding ecdsa keys 15:15:37 #link https://review.opendev.org/c/openstack/tempest/+/807465 15:16:28 from what i remember it doesn't change anything, just adds support for different keys, I need to take a look again 15:16:46 but there shouldn't be any harm to proceed, we need to start somewhere with the fips thingy 15:16:52 I will also check that, I think we have job setup in nova to run with that key and see if that is working? 15:17:11 yeah, i think it was 15:17:14 do you have that nova job patch? 15:17:20 let me check 15:17:40 #link https://review.opendev.org/c/openstack/nova/+/790519/15/.zuul.yaml#521 15:17:46 #link https://review.opendev.org/c/openstack/nova/+/790519 15:18:10 but that does not depends-on on tempest 15:18:37 ah it is 15:19:01 we need that nova job to pass first so that we can verify the tempest change 15:19:03 it does, on a third review after the one with the ecdsa keys support 15:19:10 yeah 15:19:25 ok, recheck then? or you mean to have that job gating in tempest? 15:20:29 at some point i'd like to see those jobs (at least one with fips) gating in tempest, but i'm kinda lost with all the prerequisites, like which patch needs to be merged before we can have that 15:20:31 yeah, adding in tempest will be good also to verify the change 15:20:37 i need to take a deeper look 15:21:31 added comment in that patch to add tempest job 15:21:54 without that it is difficult to check if new changes/testrs are working on service side or not 15:22:58 yeah, agree, i'll try to propose that after the meeting as a non-voting of course and then we can recheck the patch with the ecdsa keys support 15:23:14 +1, thanks 15:23:30 we can do in same patch so that we sync on merging the stack 15:24:15 yeah, good, let's move on 15:24:17 #topic Open Discussion 15:24:28 (gmann) Turning off the openstack-health service and so does retirement of it? 15:25:06 there will be a call tomorrow with the tripleo ci team where we will discuss next steps on how we can collaborate together as they are building their version of openstakc-health 15:25:29 the day after tomorrow, not tomorrow, sorry 15:25:35 kopecmartin: thanks for the call schedule. 15:25:38 let me find the emails 15:25:39 did we send on ML 15:25:52 #link http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026250.html 15:26:06 yeah Thursday December 16th 1630 UTC 15:26:08 +1 15:26:15 so in 2 days and one hour 15:26:54 the next topic is 15:26:56 (gmann) This came up during pain point discussion in TC. With fewer contributors issues in QA (especially devstack where we have more incoming requests/changes), how about expanding the devstack team with potential candidates? 15:27:02 #link https://etherpad.opendev.org/p/pain-point-elimination 15:27:15 yeah, it is just a thought in case we can extend 15:27:24 frickler: yoctozepto ianw ^^ what you think 15:27:27 are there any candidates? also it might make sense to clean up inactive cores 15:27:34 and before that we need to find the candidates 15:27:44 frickler: yeah that is good point 15:28:24 I think we can discuss on the possible candidates like we do for adding core process among us first to avoid any offending 15:28:38 I would be very glad to mentor potential candidates, but I haven't seen any 15:28:43 and then see if we can solve the issue brought up in pain point discussion 15:29:14 frickler: yeah. there were few in my thought and before i discuss about those they prioirty change 15:30:05 anyways, I just added the topic as it came up in pain point discussion but we can follow our normal process of finding the candidates first and then proceed 15:30:19 in particular there still isn't anyone with a focus on centos/fedora, would be good if someone within redhat could bring that up internally 15:30:30 I will start few on email 15:30:57 eliadcohen: ^ 15:31:04 +1, yeah good point, we have seen lot of interest from centos side on testing, py3.6 etc I think it make sense to bring this to them 15:31:20 and if they can help to maintain devstack part of that, it will be helpful 15:31:48 do we wanna write an email to ML? and let's see who'll reply 15:31:50 e.g. we need to urgently move to fedora35 I think 15:31:58 before f34 gets removed from infra 15:32:11 kopecmartin: for redhat, yes please. or you can send on rdo community ML also 15:32:28 kopecmartin: frickler for current possible candidate, let me start email among us first 15:32:55 gmann: ack 15:33:18 gmann: make sure to use my current email then 15:33:36 frickler: ack 15:34:38 anything else for the open discussion? 15:34:46 that's all from me 15:36:09 #topic Bug Triage 15:36:17 #link https://etherpad.opendev.org/p/qa-bug-triage-yoga 15:36:22 bug numbers are recorded at ^ 15:37:06 however, i don't have any specific bug to bring up 15:37:23 so if there isn't anything else to discuss, i think that's it then 15:38:19 thank you all 15:38:20 #endmeeting