13:32:23 #startmeeting qa 13:32:24 Meeting started Tue Apr 28 13:32:23 2020 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:32:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:32:27 The meeting name has been set to 'qa' 13:33:03 who all here today ? 13:33:06 hi 13:33:08 hello 13:33:44 Hi 13:33:55 hi, i'm here, but need to focus on something else right now , so i'll be only in reading mode now.. if you need anything from me, just ping me and i'll answer later 13:33:55 o/ 13:34:06 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours 13:34:09 today agenda ^^ 13:34:23 #topic Announcement and Action Item (Optional) 13:35:30 one announcement is about ussuri branch which is ready now and qa releases or to setup the devstack and grenade is in-progress 13:35:36 #link https://review.opendev.org/#/q/topic:qa-ussuri-release+status:open 13:36:13 #topic Ussuri Priority Items progress 13:36:34 #link https://etherpad.opendev.org/p/qa-ussuri-priority 13:36:49 masayukig: you have anything to share on testr.conf or plugin blacklist things ? 13:37:40 gmann: nothing particular yet. I'll start the testr.conf thing after the ussuri release 13:38:03 ok 13:38:07 #topic OpenStack Events Updates and Planning 13:38:22 we are planning V PTG now, masayukig go ahead 13:38:41 thanks. Based on the doodle voting, I've signed up QA for the following 4 hours slots in the "Icehouse" room for the Vitctoria virtual PTG. Wednesday, June 3: 13-14, 14-15 UTC and Thursday, June 4: 13-14, 14-15 UTC. 13:38:54 #link https://etherpad.opendev.org/p/qa-victoria-ptg 13:40:09 I think 4 hours are enough for our 8 topics. If you have any comments or additional topic, please let us know. 13:40:56 And, I'll send an email about this on the ML later (maybe, tomorrow) 13:41:01 +1, thanks masayukig for organizing that. 13:41:32 hope it does not conflict with nova and TC which are not yet booked. 13:41:45 that's it from my side 13:41:54 thanks again. 13:42:08 #topic Sub Teams highlights (Sub Teams means individual projects under QA program) 13:42:11 Tempest 13:42:44 there two changes in gate for Tempest 13:42:55 1. adding stable/ussuri job - #link https://review.opendev.org/#/c/723620/ 13:43:19 2. dropping stable/rocky gate job from mater - #linl https://review.opendev.org/#/c/722183/ 13:43:22 #link https://review.opendev.org/#/c/722183/ 13:43:32 masayukig: ^^ if you can look at later one 13:44:00 sure thing 13:44:24 Tempest 24.0.0 is released and it is in u-c also where few xenial job need Tempest <24.0.0 on stein onwards gate fail due to constarint. 13:44:44 i need to check what is possible way for those job to fix. sometime after office hour 13:44:53 anything else on Tempest side ? 13:45:03 I have two (probably) minor changes in tempest too 13:45:53 this one https://review.opendev.org/#/c/720213/ allows some job failure to be properly handled in cinder 13:46:06 I have my patches in the https://etherpad.opendev.org/p/qa-bug-triage-ussuri , one for discussion and others for review. If you get time, can you please look at it:) 13:46:11 see an example https://review.opendev.org/#/c/720214/ 13:46:37 and then this small tuning of the storage test blacklist file: https://review.opendev.org/#/c/721043/ 13:47:09 you mean if tempest test failing then do not fail and continue run the plugins tests ? 13:47:26 paras333: sure, we will discuss in bug toioc 13:47:28 topic 13:49:04 anyways I will check on review. 13:49:17 anything else ? 13:49:29 Patrole 13:49:49 after fixing the gate, i was able to finally release the Patrole for ussuri. 0.9.0 is released 13:50:07 same things there. dropping the stable/rocky jobs from master gate 13:50:10 #link https://review.opendev.org/#/c/722184/ 13:50:40 I will add ussuri job also there but that need some adjustment on config side. 13:51:01 Grenade 13:51:09 zuulv3 native job 13:51:11 #link https://review.opendev.org/#/q/topic:native-zuulv3-migration+(status:open+OR+status:merged) 13:51:25 base job are merged now, thanks tosky again for working on those 13:51:47 ++ 13:52:04 we need to migration now, I have pushed the tempest side changes. tricky things here is project side patch to move to new job and template on tempest side needs to go togehter 13:52:15 otherwise it end up running the same job twice with different name 13:52:43 Tempest is merge now #linl https://review.opendev.org/#/c/722551/ 13:52:49 #link https://review.opendev.org/#/c/722551/ 13:53:26 once grenade and devstack ussuri branch setup is merged we can start on project side. nova, cinder are already started 13:53:30 anything else on grenade ? 13:54:20 #topic Community goal tracking 13:54:23 #link https://etherpad.opendev.org/p/qa-community-wide-goals-tracking 13:54:35 i started the PTL and contribution guide on all QA projects 13:54:40 few are pending to merge i think 13:55:23 only two are left 13:55:25 #link https://review.opendev.org/#/c/721757/ 13:55:42 #link https://review.opendev.org/#/c/721108/ 13:56:04 we will start the V cycle goal planning soon once those are finalized from TC side 13:56:23 one goal is still yet to decide. I will bring that in TC office hour in this week 13:56:33 #topic Bug Triage 13:56:44 kopecmartin: is in read only mode i think 13:56:51 paras333: go ahead 13:56:56 you had something on bug ? 13:57:31 Nothing major, there are BZ that yet need reviews just want to bring that to everyone's attention https://etherpad.opendev.org/p/qa-bug-triage-ussuri 13:57:50 paras333: sure, thakns. 13:57:52 thanks 13:58:04 and some needs discussions , so if we can view them as well that will be great! 13:58:07 i will spend more time on those once ussuri release is finished 13:58:13 ack 13:58:15 sure thing 13:58:26 thanks 13:58:37 soniya29: anything from your side 13:58:47 sorry we missed the scenario manager things during Tempest topic 13:59:08 but we can talk here if anyting you would like to discuss/bring in notice 13:59:25 gmann: no updates for now 13:59:49 ok. 14:00:27 soniya29: feel free to ping us on channel anytime you want to discuss on that or any doubt etc 14:00:36 #topic Critical Reviews 14:00:54 any critical review other than what we discussed already ? 14:01:50 #topic Open Discussion 14:01:59 anything else to discuss today? 14:02:18 I have started poking around hacking, Is there any action item we would like to see on hacking project? 14:02:45 I have gone through the Bugs and it seems most of them are just waiting for the closures 14:02:57 paras333: not for now, incoming request are not so frequent there but if any then reviewing those will be helpful 14:03:26 sure 14:03:28 ok, please add on the etherpad if you find something need review or disucsion 14:03:45 absolutely 14:04:04 thanks for the help 14:04:11 paras333: you might want to review which local hacking rules are used in many projects and merge them into hacking itself... 14:04:23 paras333: there's quite a few check copied around 14:04:37 nothing urgent... 14:04:37 if those are common not project specific 14:04:52 gmann: sorry, double booked for a moment; regarding your question, some cinder jobs runs two sets of jobs (tempest and then cinderlib) in the same run (long story), so if tempest fails we would still like to run cinderlib tests 14:05:06 gmann: some are, question is how common 14:05:15 AJaeger: Ahh ok , I will check. Can you link me to some examples? 14:05:32 tosky: two set of job in single run ? 14:05:54 AJaeger: we have lot of tempest side which are for service client. 14:05:55 gmann: two set of tests in a single job, sorry 14:06:09 ohk :) i was confused with 'job' 14:06:15 paras333: http://codesearch.openstack.org/?q=flake8%3Alocal-plugins&i=nope&files=&repos= shows which are in use 14:07:01 tosky: i see and if tempest test finish and fail then it does not run cinderlib tests ? 14:07:17 AJaeger: ack, I will take a look 14:07:20 gmann: right now it does, because I put a ignore_errors; but then I kind of lose that status 14:07:38 the job passes globally, but it shouldn't 14:08:13 I need the status of tempest run registered somewhere (https://review.opendev.org/#/c/720213/) so that I can check it later and fails properly (https://review.opendev.org/#/c/720214/) 14:08:18 with your change, you mean it pass globally even test fail because of ignore_errors ? 14:08:24 AJaeger: thanks for link. 14:08:45 no, the change allows the job to fail; right now it is not failing because ignore_errors makes it pass 14:08:53 right now: 14:09:06 ignore_errors on cinder side job right ? 14:09:11 yep 14:09:15 - if tempest run passes and cinderlib tests pass, that's fine 14:09:32 - if tempest run passes and cinderlib tests fails, the job globally fails (correct) 14:10:03 - if tempest run fails, and cinderlib tests pass, the job is marked as passed due to the ignore_errors (otherwise it would skip cinderlibs tests) 14:10:12 i see, got it. I will check the review. 14:10:13 that's what the two fixes address 14:10:18 thanks! 14:10:38 and finally, a note about grenade: I marked all the obsolete/no more needed open grenade reviews with -1 14:10:39 i think heat also run both tests in single job but it is with tempest run 14:10:50 so if you want you can kill all those reviews 14:10:56 sure. 14:11:07 I will check sometime in this week. 14:11:08 thanks 14:11:29 anything else to discuss. 14:11:58 thanks all for joining. let's close office hour for today 14:12:04 thanks! 14:12:05 #endmeeting