15:00:29 #startmeeting qa 15:00:29 Meeting started Tue Jan 11 15:00:29 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:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:29 The meeting name has been set to 'qa' 15:00:35 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Weekly_QA_Team_meeting 15:00:38 agenda ^^ 15:01:11 o/ 15:02:25 hi, let's start 15:02:32 o/ 15:02:33 qa-yoga-priority lists incorrect QA office hours 15:03:15 ? 15:03:21 alexYefimov: you mean this one? 15:03:24 #link https://etherpad.opendev.org/p/qa-yoga-priority 15:03:27 yes 15:04:07 oh, yeah, that's another location we forgot to edit 15:04:21 it was used during the priority items planning 15:04:45 however, i see how it can be confusing 15:05:33 for the record, the current time of the meeting is always displayed here 15:05:35 #link https://meetings.opendev.org/#QA_Team_Office_hours 15:05:36 and 15:05:42 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Weekly_QA_Team_meeting 15:05:53 thanks alexYefimov, i'll fix the time in that etherpad 15:07:13 #topic Announcement and Action Item (Optional) 15:07:20 nothing specific from me here 15:07:27 #topic Yoga Priority Items progress 15:07:31 #link https://etherpad.opendev.org/p/qa-yoga-priority 15:07:35 any updates on the priority items? 15:07:45 nothing much to share today from me 15:09:16 ack, nothing from my side neither 15:09:21 #topic OpenStack Events Updates and Planning 15:09:51 i've noticed that next PTG dates have been announced already 15:09:53 #link https://www.openstack.org/ptg/ 15:09:59 yeah 15:10:05 it's gonna be virtual again 15:10:24 i'll create a new etherpad for the topics to cover 15:10:39 +1, thanks 15:11:09 moving on 15:11:10 #topic Gate Status Checks 15:11:17 #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:54 any blockers to review? 15:12:19 I have not noticed in this week 15:12:47 kopecmartin, is pythontempestconf gate stable now? 15:13:18 soniya29: i don't think so 15:13:34 that last link isn't retrieving a valid page, BTW 15:14:29 soniya29: there is at least one failure which is related to interop and all interop projects suffer from it , but we're trying to get to bottom of it 15:14:37 jelabarre-rh: hmm, it works for me 15:14:41 hmmm... did a copy/paste and it worked 15:14:52 kopecmartin, okay 15:15:04 just however hexchat sent it then. nevermind 15:15:19 :) 15:15:24 #topic Periodic jobs Status Checks 15:15:28 #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:15:34 #link https://zuul.openstack.org/builds?project=openstack%2Ftempest&project=openstack%2Fdevstack&pipeline=periodic 15:15:47 all seems good 15:16:10 #topic Sub Teams highlights 15:16:14 Changes with Review-Priority == +1 15:16:21 #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:16:42 5 changes there ^ 15:16:55 i reviewed some, I'll try to check the rest soon 15:17:09 anyone feel free to check and review them too 15:17:20 feel free to complain if I spread too many +1s there 15:17:21 kopecmartin, reviewed a few today morning 15:18:13 frickler: it's fine, even better, i don't have always time to check for example devstack patches specifically , this helps me 15:18:52 lib/neutron deprecation lgtm, +A 15:19:15 in general , i think that having priority +1 on patches which were already reviewed by one core is great, it speeds the process up 15:19:29 kopecmartin: I see any changes. Do I need permissions changed? 15:19:49 just a question, is it mandatory to have primary, alt, admin, roles from different projects within tests? 15:20:28 alexYefimov: you don't see anything when you open this ? 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:20:51 Error 400 (Bad Request): line 1:180 mismatched input '' expecting ')' Endpoint: /changes/ 15:21:41 soniya29: no, it depends on what to test in test case. it may need those if they are verifying the cross project resources 15:22:08 alexYefimov: you may need to be logged in before opening that link 15:22:26 gmann, so it will depend on the test case, right? 15:22:33 alexYefimov: hmm, that's weird, maybe your irc client changes that link somehow when you click on it or copy from it? 15:22:37 soniya29: right 15:22:48 kopecmartin: I am logged ... can seem my name 15:22:48 i tried to open in in a private window, being logged in/out shouldn't matter 15:22:53 yeah, try copy paste 15:23:15 same error 15:23:33 gmann, today i was reviewing a patch where i found this - https://review.opendev.org/c/openstack/tempest/+/819284 15:24:03 soniya29: ok, I will check it 15:24:26 alexYefimov: are you able to open this ? https://review.opendev.org/q/project:openstack%252Ftempest 15:25:14 gmann, since we are saying it will depend on the test case, we dont need to do any modification in tempest with intention of having different roles / same roles 15:25:18 or try https://fricklercloud.de/devstack-rp1 15:25:27 gmann, link works fine 15:25:39 both work fine 15:26:22 humm, then it should work as that also a query of gerrit 15:26:33 o.k., the latter is a redirect to the same thing that kopecmartin shared 15:26:40 soniya29: I need to check in review, have not looked yet 15:27:13 gmann, take your own time, i was just curious so i asked :) 15:27:25 soniya29: sure. thanks 15:28:16 let's move on 15:28:18 #topic Open Discussion 15:28:37 regarding openstack-health 15:29:39 arxcruz|ruck: will focus on their (tripleo's) dashboard and then if there will be need to resurrect that one functionality (test pass/fail rate) we'll have a look again 15:29:57 until then, no work regarding openstack-health will be done, we just need to prioritize other things atm 15:31:10 that's to conclude our last week's discussion 15:31:27 any updates regarding the expanding the devstack team with potential candidates? 15:31:38 so no volunteer for maintaining the o-h ? 15:32:24 we are facing this issue with many projects, devstack, o-h, patrole 15:32:47 not yet, arxcruz|ruck mistaken this o-h for their o-h 15:33:06 oh 15:33:26 however, I'm planning to do a few experiments with it locally, so that i get better understanding of it, might help in the future if we wanted to resurrect the service 15:33:39 so we may postpone the repo retirement 15:34:08 mtreinish looked at the current failure and it is in subunit2sql, and few workaround to fix it with sqlalchemy cap or so 15:35:05 what does it mean now? will it function if we find a new hosting? 15:35:57 kopecmartin: I do not think that is fixed. but yes hosting is next things we need to discuss. 15:37:29 so we're almost at the beginning again :D 15:39:05 yeah, we still need someone to take care of o-h maintenance which is not large work but still need someone. 15:39:39 ok, let's do this, let me take a look at it and experiment with it locally first 15:39:54 and let's discuss after that 15:40:06 sounds good 15:40:25 any updates regarding the expanding the devstack team with potential candidates? 15:41:42 kopecmartin, i can help there but i am already occupied so not sure about bandwidth 15:42:07 soniya29: o-h or devstack? 15:42:13 kopecmartin, devstack 15:42:45 kopecmartin: not yet. I again forget. I will send today after meeting 15:43:45 soniya29: thanks, i see you also wanted to help with one of the items on our priority list, that's a lot of work , take it easy :) 15:43:49 gmann: ok, np , thanks 15:44:04 ok then, anything else for the open discussion? 15:44:17 kopecmartin, yeah, that's why i am not sure :) 15:44:47 there were two new devstack bugs about pip install failing 15:44:58 I could not reproduce and asked for more information 15:45:17 but maybe someone else has an idea 15:45:28 #link https://bugs.launchpad.net/devstack/+bug/1957048 15:45:46 #link https://bugs.launchpad.net/devstack/+bug/1956928 15:46:00 i've noticed that the devstack numbers went down, thanks frickler for triaging 15:46:02 #link #link https://etherpad.opendev.org/p/qa-bug-triage-yoga 15:46:03 #link https://etherpad.opendev.org/p/qa-bug-triage-yoga 15:48:10 i had also an issue with running ./stack.sh again (after ./unstack.sh and ./clean.sh) , something with py3.8 , maybe pip too, i don't remember 15:48:23 i didn't have time so i just started on a new clean vm 15:48:40 but maybe that's the reproducer, to deploy it, then clean, unstack and deploy again 15:49:29 ah, I only do unstack, no clean, will give it another try with that 15:50:18 yeah, usually clean work for me but have not tried recently 15:50:56 gmann: regarding this bug 15:50:57 #link https://bugs.launchpad.net/tempest/+bug/1948935 15:51:03 we have 2 options how to address that 15:51:22 1. leave the --concurrency arg as it is and proceed with the proposed patch 15:51:22 2. improve the documentation of the argument as you suggested in the other comment and rename the argument as well - let's go with something like --creds-number 15:53:24 kopecmartin: not sure about 2nd one as concurrency seems easy to understand? like what we have in tempest or stestr 15:54:00 kopecmartin: current proposed patch make it more confusing like it double the concurrency so no way to generate/run serially 15:54:34 I was suggesting to change the default value instead of hard coding it with *2 https://review.opendev.org/c/openstack/tempest/+/822434/2/tempest/cmd/account_generator.py 15:54:37 #link https://review.opendev.org/c/openstack/tempest/+/822434/2/tempest/cmd/account_generator.py 15:55:24 i see, so we can just increase the default value (1->2) 15:56:05 that sounds good and easy enough 15:56:24 yeah, as that is most test case requirement is. and anyone need single creds can change it to 1 15:56:47 prefect, let's go with that then 15:57:07 that's it 15:57:12 anything else to discuss? 15:57:51 nothing else from me 15:58:01 nothing from my side 15:58:07 thank you all for attending, see you next week 15:58:12 #endmeeting