15:00:13 #startmeeting qa 15:00:13 Meeting started Tue Mar 15 15:00:13 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:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:13 The meeting name has been set to 'qa' 15:00:21 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Weekly_QA_Team_meeting 15:00:21 kopecmartin, hello 15:00:22 agenda ^^ 15:00:26 soniya29: hi 15:01:06 o/ 15:01:37 o/ 15:01:39 let's start 15:01:45 #topic Announcement and Action Item (Optional) 15:01:55 we have release a new version / tag of tempest 15:01:58 30.0.0 15:02:57 gmann: anything else we need to do? i'm checking the qa's release wiki page 15:02:58 #link https://wiki.openstack.org/wiki/QA/releases 15:03:45 w.r.t. devstack and grenade we're waiting for a stable branch i guess 15:04:22 I think yes, for tempest all good. and next is to wait for signal from release team once we need to start the devstack and grenade things 15:04:28 elodilles: ^^ 15:04:50 good 15:05:04 #topic Yoga Priority Items progress 15:05:04 #link https://etherpad.opendev.org/p/qa-yoga-priority 15:05:07 any updates? 15:05:30 yes 15:06:01 Stephen Finucane proposed openstack/hacking master: Update CI to use unversioned jobs template https://review.opendev.org/c/openstack/hacking/+/833811 15:06:22 https://review.opendev.org/q/topic:tempest-scenario-manager-cleanup+project:+openstack/barbican-tempest-plugin+owner:+self 15:07:14 soniya29: you are including self in query. you mean this series right? #link https://review.opendev.org/q/topic:tempest-scenario-manager-cleanup+project:+openstack/barbican-tempest-plugin 15:07:32 gmann, yeah 15:08:06 nice, there are many patches incomming related to the cleanup 15:08:08 #link https://review.opendev.org/q/topic:tempest-scenario-manager-cleanup 15:08:13 thank you soniya29 and rpopelka 15:08:26 apart from this 15:08:27 i'm gonna review (at least some) right after this meeting 15:08:31 soniya29: why we are replacing the methods one by one instead of replacing whole scenario manager? 15:08:58 at least for all methods we have in tempest.scenario manager as stable 15:09:09 gmann: plugins may have their own custom methods in there 15:09:24 plus it's easier to have smaller reviews 15:09:33 gmann, we have some customization in the plugin methods 15:09:57 gmann, so need to review the method implementation first and the remove them 15:09:58 kopecmartin: yeah, I mean just leave those and replace everything in one shot ? there are less plugins having their custom method 15:10:18 soniya29: I doubt, bcz I copied them as it is from what tempest has 15:10:59 in next meeting, i will make a list of those custom methods, so that we can discuss about them 15:11:24 but yes there are such methods whose implementation varies from tempest scenario manager 15:11:58 for example, barbican case what is the last patch? is this? #link https://review.opendev.org/c/openstack/barbican-tempest-plugin/+/833801 15:12:00 gmann, kopecmartin, also i found that in some methods we are missing on some clients in tempest 15:12:16 gmann: well, sure, if there is a plugin, which doesn't have anything custom in their manager, we can do that in one shot, but there might be even a small customization, like port name, let's take blazar as an example - https://review.opendev.org/c/openstack/blazar-tempest-plugin/+/830595/5/blazar_tempest_plugin/tests/scenario/manager_freeze.py 15:12:36 gmann, yes, that's the last one i posted 15:13:33 soniya29: it is hard to see the series, is it new gerrit UI or just me not able to see the dependencies? you did it with dependencies right? not all patch as separate in barbican tempest plugin? 15:14:11 gmann: i don't think they are dependent 15:14:12 kopecmartin: yeah for such plugins we can do in multiple steps. 15:14:15 do they need to be? 15:14:16 gmann, i have dependencies on tempest 15:14:26 s/have/have added 15:14:46 because we are missing some clients in tempest which are available in plugin 15:14:57 here barbican-tempest-plugin 15:14:59 kopecmartin: soniya29 ok then you will have merge conflict if single plugins changes are not dependent 15:15:27 oh, yeah , that's true 15:15:39 but first someone from the plugin needs to review 15:15:51 that is why i was confused on how to review it and see what is end pic of scenario manager 15:16:08 anyways I will review them and put comment there 15:16:39 gmann, kopecmartin, https://review.opendev.org/c/openstack/tempest/+/833788 15:16:55 https://review.opendev.org/c/openstack/tempest/+/833758 15:16:58 kopecmartin: I think we can also verify it with what implementation we have or via git history is easy. 15:17:41 soniya29: ok so those are conflict and plugins cannot use it from master 15:18:19 or everything is from master now? 15:19:18 soniya29: please rebase those 2 patches in tempest, put one of them on top of the other .. we can merge them , however, plugins will be able to use them in a few cycles, not right now 15:19:34 otherwise we would break the plugins compatibility with the older tempest 15:19:35 gmann, i am not sure :) 15:19:53 kopecmartin: I am trying to recall on that why we waited for replacement until train use old tempest? 15:20:09 ohk 15:20:15 kopecmartin, okay 15:20:27 so if plugin master is using the old tempest and these new things can break them 15:20:39 gmann: i think we waited a few cycles only because we didn't want to make the plugins incompatible with one release older tempest 15:20:45 yeah 15:21:08 and we kinda agreed that a few cycle difference = a few releases of tempest (3?) are enough 15:21:12 kopecmartin, gmann, and we wait more now then we will have more divergence i guess :) 15:21:32 s/and/and if 15:21:45 kopecmartin, yupp 15:21:51 soniya29: we can do place the things what present in tempest 27.0.0 not what we moved/added after that 15:22:06 I will review those patches and add detail comment. 15:22:14 gmann, sure 15:22:34 i'll review too 15:22:37 good 15:23:10 any other updates regarding the priority items? 15:24:02 nope 15:24:04 yeah, let's review and decide the direction before we have lot more patches 15:24:08 nothing else from me 15:24:23 gmann: you mean right now? 15:25:04 kopecmartin: i mean in review 15:25:16 oh, yeah, we can do that , sure :) 15:25:32 moving on then 15:25:33 #topic OpenStack Events Updates and Planning 15:25:35 or we can discuss in PTG 15:25:41 we have etherpad for the topics to discuss during PTG sessions 15:25:47 #link https://etherpad.opendev.org/p/qa-zed-ptg 15:25:51 if review comments are not understandable or easy to understand. 15:25:58 anyone, please add there any topic you want to discuss 15:26:01 gmann: i agree 15:26:24 gmann, sure 15:26:34 in the ptg etherpad time slots we booked for QA can be found as well 15:26:51 kopecmartin: soniya29 added it in etherpad, I will add detail/overview later 15:27:03 gmann: perfect 15:27:14 so we can reivew add our thoughts and then discuss and finalize the direction in PTG 15:27:18 i have to add a few topics too, can't force myself to write it up 15:27:32 gmann: +1 15:27:42 gmann, till then, should we slow down/stop the patches? 15:28:20 soniya29: let's see based on the number of comments and things raised in them 15:28:51 kopecmartin, sounds good :) 15:29:28 yeah 15:29:37 #topic Gate Status Checks 15:29:44 #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:30:04 one review there 15:30:18 i workflowed that tls-proxy patch 15:30:22 frickler: dansmith ^^ 15:30:33 thanks 15:31:02 dansmith: thank you for chasing the errors 15:31:14 now let's see what will get broken :D 15:31:24 yep :) 15:31:38 .. i think it will be fine, either way we would need to address that , sooner or later 15:32:15 #topic Periodic jobs Status Checks 15:32:21 #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:32:26 #link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic 15:32:32 seems all good there 15:32:39 #topic Sub Teams highlights 15:32:44 Changes with Review-Priority == +1 15:32:50 #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:33:05 no changes 15:33:14 #topic Open Discussion 15:33:19 anything for the open discussion? 15:34:17 nothing else from me. I need to find time to check the SSH-able failure on rescue tests. I will try today or tomorrow 15:34:58 ok, thanks gmann 15:35:04 #topic Bug Triage 15:35:09 #link https://etherpad.opendev.org/p/qa-bug-triage-yoga 15:35:39 i see a decrease in open/new bugs for tempest and devstack projects, thank you for triaging 15:36:18 that's all from my side 15:36:25 thank you everyone 15:36:28 see you around 15:36:32 kopecmartin, thanks :) 15:36:36 #endmeeting