14:00:15 #startmeeting qa 14:00:16 Meeting started Tue May 4 14:00:15 2021 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:19 The meeting name has been set to 'qa' 14:00:21 who all here today? 14:00:41 \o/ 14:01:27 hello 14:01:56 let's start 14:02:13 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours 14:02:17 today agenda ^^ 14:02:25 #topic Announcement and Action Item (Optional) 14:02:31 no action item form previous meeting 14:02:41 I do not have any announcement too 14:02:53 #link Xena Priority Items progress 14:03:10 #topic Xena Priority Items progress 14:03:27 #link https://etherpad.opendev.org/p/qa-xena-priority 14:04:03 I pushed some of the patches for plugins+tempest master testing and run-tempest role 14:04:21 but could not make much progress for their results and checking with requirement team 14:04:30 I will do that this week 14:04:45 any other updates on any of the Xena item? 14:05:44 na-ah 14:05:54 #topic OpenStack Events Updates and Planning 14:06:11 nothing on this, we finished the PTG and kopecmartin summarized it on ML too. 14:06:22 #topic Gate Status Checks 14:06:44 one race happening in image import tests were fixed #link https://review.opendev.org/c/openstack/tempest/+/788856 14:07:11 any other failure you are seeing on gate? (any project but related to QA) 14:07:54 nothing reported to me, though I wonder if mrunge succeeded fixing gates for telemetry 14:08:09 ok 14:08:26 #topic Periodic jobs Status Checks 14:08:27 gates for telemetry still in semi-good shape 14:08:37 #link https://zuul.openstack.org/builds?job_name=tempest-full-victoria-py3&job_name=tempest-full-ussuri-py3&job_name=tempest-full-train-py3&pipeline=periodic-stable 14:08:38 mrunge: any way QA could help? 14:08:55 #link https://zuul.openstack.org/builds?job_name=tempest-all&job_name=tempest-full-oslo-master&pipeline=periodic 14:09:07 mrunge: yeah, what are the failure? 14:09:12 good question. It would be awesome if more people would look at stable jobs and also on periodic jobs 14:09:43 I wonder if you could introduce us to the issues 14:09:48 are you tracking them somewhere? 14:09:50 for now, I have switched integration tests to non-voting 14:10:13 other than trying to remember, I am not tracking it somewhere. but I should 14:10:16 blasphemy in this channel :D 14:10:47 not sure if this would derail discussion in this meeting? 14:10:56 this is office hours 14:11:08 yeah we can discuss now or later also. 14:11:18 feel free to ping us 14:11:19 integration tests fail in clean-up phase 14:11:28 thank you, I really appreciate it 14:11:52 all right, any details, name of the job? 14:12:08 just a sec, will look it up 14:12:24 i think this one? https://review.opendev.org/c/openstack/telemetry-tempest-plugin/+/787739 14:12:26 #link https://review.opendev.org/c/openstack/telemetry-tempest-plugin/+/787739 14:12:51 that's the link of switching it to non-voting 14:13:04 Details: {'type': 'SecurityGroupInUse', 'message': 'Security Group e5f886b0-4a09-4348-88cc-efd4a5ea34c3 in use.', 'detail': ''} 14:13:11 yes 14:13:19 interesting 14:13:30 anyways let's debug it after office hour. 14:13:35 yes 14:13:50 any other gate failure we need to keep eyes/help on? 14:14:25 ok, let's move then 14:14:28 periodic jobs 14:14:35 #link https://zuul.openstack.org/builds?job_name=tempest-full-victoria-py3&job_name=tempest-full-ussuri-py3&job_name=tempest-full-train-py3&pipeline=periodic-stable 14:14:36 #link https://zuul.openstack.org/builds?job_name=tempest-all&job_name=tempest-full-oslo-master&pipeline=periodic 14:14:39 they seems green 14:14:44 periodic happy 14:14:58 yeah 14:15:01 #topic Sub Teams highlights 14:15:06 Tempest 14:15:17 #link https://review.openstack.org/#/q/project:openstack/tempest+status:open 14:15:52 nothing on Tempest to discuss 14:16:10 Patrole 14:16:20 #link https://review.opendev.org/q/project:openstack/patrole+status:open 14:17:04 few open reviews but seems gate is not happy there. I will check and fix it if any service policy is changed 14:17:15 #action gmann to check/fix the patrole gate 14:17:22 Devstack 14:17:32 #link https://review.opendev.org/q/project:openstack/devstack+status:open 14:17:53 always something open 14:17:55 one is Drop Bionic support 14:18:12 we are getting response on ML from projects on confirmation about this 14:18:45 #link http://lists.openstack.org/pipermail/openstack-discuss/2021-April/022141.html 14:18:45 yeah, but it seems projects understand the need well 14:19:18 yeah, 14:19:45 what date we should merge the devstack? 14:20:00 i said 2nd week of May in ML 14:20:15 which can be 14th May as last 14:20:21 I agree that should be just fine 14:20:24 ok 14:20:35 let's see what opendev does with the base job as well 14:20:41 still 10 more days to fix if needed 14:20:44 yeah 14:20:44 that could be funnier 14:20:57 agree 14:20:58 well, at this point in cycle it should be relatively safe 14:21:04 let's see 14:21:13 we can't stay on bionic forever anyway 14:21:27 yeah, from devstack side I am sure we will get complained on 3rd party CI side 14:21:44 yeah, but what can we do 14:21:44 as what happened in xenail case 14:22:09 yoctozepto: nothing, we notified them and asked them to migrate in many platform 14:22:19 well, at least now we are not switching python version as well 14:22:29 so if anyone ask us to fix for Bionic we just tell them to migrate to Focal 14:22:41 good point, so less breakage may be 14:22:51 now print it and put it in a frame :D 14:22:59 "so if anyone ask us to fix for Bionic we just tell them to migrate to Focal" 14:23:02 :) 14:23:14 anything else on devstack? 14:23:23 nope 14:23:27 ok 14:23:28 Grenade 14:23:42 #link https://review.opendev.org/q/project:openstack/grenade+status:open 14:24:49 you know my opinion 14:25:03 but at least it's shorter than devstack's 14:25:06 :-) 14:25:13 :) 14:25:19 perhaps we could abandon old ones 14:25:25 I will check this patch after office hour #link https://review.opendev.org/c/openstack/grenade/+/788239 14:25:45 yeah, I will see what all are fine to continue otherwise we can cleanup 14:25:53 gmann, can we close this out since it is not updated from feb 2019 :- https://storyboard.openstack.org/#!/story/2004771? 14:25:58 regarding that review 14:26:08 I wonder if we need those files any more 14:26:19 but dropping that part should not hurt anyway 14:26:35 I understand grenade was meant to upgrade any->any 14:26:48 yet ended up any->+1 14:27:15 yeah, will be ok but will check the placement things workaround. I do not think we need it 14:27:29 soniya29: i see this patch is not yet merged #link https://review.opendev.org/c/openstack/patrole/+/630647/ 14:27:37 soniya29: any other commit fixed that? 14:28:31 gmann, I dont think so, atleast I am not aware of any such 14:30:01 soniya29: ok, may be we can see if that is still happening or not then close or fix 14:30:03 fix 14:30:07 gmann, Do we require this fix any more? 14:30:26 I need to check what was failure, will do and comment after office hour 14:30:35 sure 14:30:52 thanks for brining this up 14:30:54 Hacking 14:30:59 any news on hacking? 14:31:47 it's happy with its review queue down to 0 waiting for review 14:31:54 +1, nice 14:32:00 thanks for help there 14:32:01 (just 1 with -1 from zbr) 14:32:06 sure thing 14:32:22 but most thanks go to zbr for his cleanup 14:32:34 yeah thanks zbr 14:32:37 #topic Gate Blocker Fix / Urgent Change 14:32:47 #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) 14:32:50 nothing there 14:33:01 #topic Open Discussion 14:33:06 nothing here too 14:33:19 #topic Bug Triage 14:33:30 #link https://etherpad.opendev.org/p/qa-bug-triage-xena 14:33:38 I will check if any critical bugs 14:34:02 no critical one 14:34:48 any bug we want to discuss today otherwise I will close office hour and go for breakfast :) 14:35:15 oh no, office hours before breakfast, how could they 14:35:24 enjoy your meal :-) 14:35:50 I usually do during it when kopecmartin chair it :) 14:36:20 understood 14:36:26 thanks everyone for joining. be safe and take care. 14:36:30 #endmeeting