14:02:15 #startmeeting qa 14:02:16 Meeting started Tue Dec 15 14:02:15 2020 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:02:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:02:21 The meeting name has been set to 'qa' 14:02:27 who all here today? 14:02:33 hi o/ 14:02:40 o/ 14:04:22 let's start 14:04:40 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours 14:04:44 ^^ today agenda 14:04:53 #topic Announcement and Action Item (Optional) 14:05:19 no action item from previous meeting 14:05:49 skipping event thing as no coming planned event yet 14:05:52 #topic Gate Status Checks 14:06:01 there are many failure in gate in last week 14:06:36 stable/rocky is still broken due to stackviz pulling the latest requirement on py3.5 14:07:12 #link http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019431.html 14:07:37 amotoki: and I are trying few fixes for that. I will continue on this after office hour 14:08:02 #link https://review.opendev.org/c/openstack/stackviz/+/767063 #link https://review.opendev.org/c/openstack/horizon/+/767066 14:08:41 bandit fixes are not landed in stable/train yet #link https://review.opendev.org/c/openstack/devstack/+/766622 14:09:09 lyarwood commented on review about the current failure on that patch which are valid one and need to fix first 14:09:10 yup, broke on sdk 14:09:37 yoctozepto: do we have fix up? 14:10:04 not one that I know of 14:10:22 ok 14:10:24 worth focusing on it I guess 14:10:43 yeah, stable/rocky is EM so let priority on stable/train first 14:11:43 any other gate failure need more attention ? 14:12:33 do we have periodic jobs to check our stable gate is healthy? 14:12:46 we usually detect our breakage when soemone proposes a backport. 14:12:58 yes, we have tempest job also running periodic for stable 14:13:28 amotoki: #link https://github.com/openstack/tempest/blob/master/zuul.d/project.yaml#L137 14:13:51 we run for all stable branch but how much we monitor that is question 14:14:00 may be we should check those in office hour at elast 14:14:03 least 14:14:03 okay, so perhaps we need to check job results periodically 14:14:08 yeah 14:14:37 #action gmann add periodic jobs result checks in office hour agenda 14:14:47 thanks. we already have good stuffs :) 14:15:46 let's keep working on current failure after office hour on priority 14:15:52 #topic Sub Teams highlights 14:16:07 Tempest 14:16:44 I have started the release process to end the support of stable/stein which is now Extended maintenance now 14:16:46 same for patrole 14:16:57 I will push the release patches today 14:17:39 Devstack 14:17:54 anything else on devstack side other than the current gate failure on stable 14:18:37 Grenade ? 14:19:36 Hacking 14:20:26 I saw project started moving towards 4.0.0. at least during the l-c failure where we had conflcit on pyflake and hacking version things 14:20:46 #topic Community goal tracking 14:20:55 #link https://etherpad.opendev.org/p/qa-community-wide-goals-tracking 14:21:33 I have marked both goal as no work for QA repo 14:21:45 I will remove it from agenda also for Wallaby cycle. 14:22:01 #action gmann remove community goal tracking from agenda 14:22:11 #topic Gate Blocker Fix / Urgent Change 14:22:30 for gate failure fixes we already discussed. 14:22:39 any other urgent review request ? 14:23:41 #topic Open Discussion 14:24:03 nothing on agenda so let's move 14:24:06 #topic Bug Triage (last 30 min) 14:24:09 kopecmartin: go ahead 14:24:43 may be a quick update if you have otherewise we can skip the bug triage today and work on gate failure ? 14:24:53 i don't have any updates regarding bug triaging .. i've been working on some refstack, refstack-client and tempestocnf maintenance 14:25:06 ok, thanks 14:25:30 let's close the office hour then. thanks all for joining 14:25:35 #endmeeting