13:30:42 #startmeeting qa 13:30:43 Meeting started Tue Apr 14 13:30:42 2020 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:30:44 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:30:47 The meeting name has been set to 'qa' 13:30:48 who all here today ? 13:30:53 hi 13:31:01 hi 13:31:10 hi 13:31:15 hello 13:32:14 let's start 13:32:22 sure 13:32:36 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours 13:32:41 Agenda for today ^^ 13:32:51 #topic Announcement and Action Item (Optional) 13:33:13 First announcement is we have new PTL now masayukig. 13:33:46 gmann: thanks for the announce :) 13:33:51 congrats masayukig 13:33:56 congrats masayukig!! 13:34:06 congrats masayukig 13:34:14 kopecmartin: paras333 bigdogstl thanks!! 13:34:39 #topic Ussuri Priority Items progress 13:35:05 We passed the m-3 last week 13:35:08 #link https://etherpad.openstack.org/p/qa-ussuri-priority 13:35:37 let's review the pending items we targeted for Ussuri 13:35:38 Remove/migrate the .testr.conf to .stestr - masayukig 13:36:09 sorry, no progress from my side atm 13:36:18 ok 13:36:19 RBAC testing strategy (reader/member/admin X project/domain/system) 13:36:40 I have to review the pathes may be in this week later once i finish my FFE items 13:36:53 How to remove tempest plugin sanity BLACKLIST 13:36:56 masayukig: ^^ 13:36:56 let me know masayukig , if you need more hands, I have a bandwidth this week probably I can help 13:37:29 masayukig: that is to some policy we need to document ? 13:37:52 paras333: thanks! I need to figure out what we should do. 13:37:56 gmann: yeah 13:38:15 masayukig: i see, so we have time for that no rush 13:38:18 Adding New glance tests to tempest 13:38:52 i have reviewed the multi store patches on devstack side. also setup new job for glance. I will check with Abhishek if anything else he need help from QA 13:39:12 Improving Tempest cleanup 13:39:17 kopecmartin: ^^ 13:39:33 we definitely improved some things but 13:39:50 as cleanup is also a topic in next ptg discussions this effort will be moved to the next cycle 13:40:46 cause there are still things to improve .. that's all i have on this right now 13:40:46 kopecmartin: ok, and your current patch is working with separate var things for cleanup and init-saved ? 13:41:11 gmann: yes, i think it is, i left you some comments there 13:41:32 kopecmartin: cool. I will check those and yeah let/s discuss it in PTG also 13:41:34 maybe others can check them too, to gather what they think about it 13:41:34 thanks 13:41:58 #topic OpenStack Events Updates and Planning 13:42:25 as you know we will have virtual PTG which will be announced soon about time, dates and channel 13:42:48 it will be challenge for us as we are distributed in all different TZ 13:42:57 yeah, 13:43:09 there's not perfect time slot.. 13:43:15 but i think time around this office hour can be ok or little early 13:43:30 yup, agree 13:43:36 yeah, that's good 13:43:45 make sense! 13:43:55 anyways we will sort out the time things once we have exact dates. 13:44:38 #link https://etherpad.opendev.org/p/qa-victoria-ptg 13:44:38 ++ 13:45:13 ^^ this is etherpad, please add the topics you would like to disuses. accordingly we will be able to plan the time for discussions. 13:45:26 ack 13:45:37 sure 13:45:39 we don't need "approval" basically :p 13:46:00 to attend the virtual PTG 13:46:36 It should be free right?:) 13:46:52 as all of us working from home it should be ok but if office is tracking day time then there will be some stattements from foundation to tell your manager about night time working 13:47:00 if that is in your night time 13:47:08 paras333: yes, free 13:47:34 ah, I need to get an approval from my family :p 13:47:53 last week we had meeting to capture the important point, you can see the detail discussion here 13:47:56 #link https://etherpad.openstack.org/p/Virtual_PTG_Planning 13:48:54 gmann: thanks, I'll look at it 13:48:59 anything on PTG topic ? 13:49:31 nothing from my side 13:49:37 adding roles list conf support to primary and alt cred in both dynamic and preprov cred manager 13:49:47 #topic Sub Teams highlights (Sub Teams means individual projects under QA program) 13:49:57 Tempest 13:50:10 bigdogstl: roles list mean ? 13:50:36 allow to run specific role for primary and alt creds 13:51:10 that means different cred then. primary is member role. 13:51:25 yes 13:51:41 that does not work downstream for us due to RBAC roles 13:51:55 I was thinking of doing a spec 13:52:14 and those are new defaults like reader etc or some customize role ? 13:52:21 to talk more about it over using existing bug and want to get feed back on the direction 13:52:49 https://bugs.launchpad.net/tempest/+bug/1738076?comments=all 13:52:49 Launchpad bug 1738076 in tempest "primary and alt credentials not flexible enough in non deafult policy.json deploymet" [Undecided,Incomplete] - Assigned to Sangeet Gupta (sg774j) 13:54:05 bigdogstl: issue is Tempest run on default policy things. but I would like to see the detail in spec. please write one and we have discuss it more there 13:54:18 will do thanks 13:54:22 thanks 13:54:29 Patrole 13:54:46 gmann: regarding scenario manager, I am starting with finding common methods within various tempest plugins. 13:55:09 soniya29: plugins's scenario manager ? 13:55:24 gmann: stable plugin manager effort 13:55:36 gmann: https://etherpad.opendev.org/p/tempest-scenario-manager 13:56:13 you mean what all methods from Tempest's scenario manager are being used in plugins via their own scenario manager copy ? 13:56:23 gmann, yeah 13:57:01 i see. cool 13:57:34 gmann, once we get those common methods, we can have a discussion for which methods to be there in stable manager to proceed further 13:57:52 one way is to prepare the current Tempest scenario manager itself as stable i mean if few methods are only used in Tempest and make sense to be stable so that any plugins can use. 13:58:12 that will be easy approach 13:58:42 gmann, okay 13:58:57 because we cannot move scenario manger to /lib because it has CONF objects so we will keep it in same place as it is currently and declare stable for plugins. like we did for test.py 13:59:28 gmann: yeah, but I'm not sure it's stable enough. some refactoring might be needed, I guess. 13:59:47 soniya29: but your audit for plugins can bring few more methods to Temepst scenario manger is more than one plugins are using those and make sense to be added in Tempest 13:59:58 masayukig: yeah that is soniya29 and kopecmartin working on 14:00:08 Yeah I think i have seen some of compute/volume scenario test using the same method logic but instead having it's own manager so may be we can start from them and have a patch and then go for rest 14:00:13 #link https://etherpad.opendev.org/p/tempest-scenario-manager 14:00:16 soniya29++, kopecmartin++ great :_ 14:00:29 masayukig: ^^ this etherpad we started. 14:00:48 gmann: thanks, I'll have a look 14:01:00 paras333: on plugins side ? 14:01:16 yup 14:02:10 ok, yeah we can move them 14:02:41 soniya29: kopecmartin our main goal is to remove the scenario manager copy from plugins and make them use of tempest stable version 14:02:59 exactly 14:03:10 gmann, yeah 14:04:15 cool 14:04:24 thanks for starting this. 14:04:37 going back to Patrole 14:05:03 gate might be broken now as nova policy granular changes. I will check that tomorrow 14:05:08 Grenade 14:06:01 seem like ironic inspector grenade jobs is broken for service available things. it was fixed for ironic but now happening for ironic inspector 14:06:23 yep, I was talking with iurygregory about that, it may be specific to that component 14:06:51 I will check after meeting 14:06:55 he was going to override tempest_concurrency, but I haven't checked whether a new patch is out 14:07:15 ok 14:07:16 tosky, it's not zuulv3 related the failures gmann is pointing =) 14:07:36 iurygregory: not the same it was fixed for ironic stable grenade ? 14:07:40 dsvm seems broken because can't check ipv4 in the port =) 14:07:46 even better (for grenade jobs; not for the global status of the gates) 14:07:54 gmann, ironic-grenade seems totally fine 14:07:58 ohk 14:08:19 iurygregory: and that thing with concurrency? Did it work, or is it not needed? 14:08:21 i will check the dtantsur patch after meeitng #link https://review.opendev.org/#/c/719873/ 14:08:23 and it was for stable/stein the problem 14:08:55 tosky, the change took effect I'm looking now at the logs to see if missed some configs =) 14:09:25 thanks 14:09:49 yw 14:10:44 let's move next. 14:10:58 #topic Community goal tracking 14:11:21 py2 drop is complete and contributor guide is in my list for this week. 14:11:31 need to write some PTl guide too 14:11:33 #link https://etherpad.opendev.org/p/qa-community-wide-goals-tracking 14:11:40 and release things, 14:12:01 * gmann may be on friday with beer... 14:12:14 The second one is really important for me :) 14:12:46 masayukig: both i think :) i am writing for you 14:13:02 gmann: thank you so much!! cheers! 14:13:19 masayukig: anyways we need to do releases for ussuri for QA tools. I will coordinate with you on that. 14:13:25 #topic Bug Triage 14:13:40 #link https://etherpad.opendev.org/p/qa-bug-triage-ussuri 14:13:42 gmann: great 14:14:33 kopecmartin: ^^ 14:14:35 i don't have many updates regarding bug triage, numbers are still decreasing which is great .. otherwise everyting is mentioned in that etheprad, have a look when have some time 14:15:17 I have couple bugs waiting for review, It's in the etherpad 14:15:21 kopecmartin++ great for the decreasing! 14:16:09 ok, let's review those in etherpad and also the review for bug fixes 14:16:21 anything else on bug or any critical bugs to dicuss ? 14:16:27 discuss 14:16:36 what is the process to move a bug from incomplete to new 14:16:53 after leaving comment do I change the bug state? 14:17:09 bigdogstl: you can comment on the pending things/question on bug and then we will move that to New 14:17:12 here is the bug in question https://bugs.launchpad.net/tempest/+bug/1738076?comments=all 14:17:12 Launchpad bug 1738076 in tempest "primary and alt credentials not flexible enough in non deafult policy.json deploymet" [Undecided,Incomplete] - Assigned to Sangeet Gupta (sg774j) 14:17:21 There are lot of bugs that seems old and no one is responding on that, Is that OK to close them if nobody respond for like 1 week or 2? or Is there any process we need to follow? 14:17:22 ok, thanks 14:18:23 paras333 I like that direction 14:18:23 bigdogstl: it is timeout while i am moving that. i will check later and move it to new 14:18:24 paras333: if you mark a bug as Incomplete it'll be marked as Invalid after some time automatically if new info is not provided 14:18:48 ahh ok that's great kopecmartin 14:18:52 kopecmartin: ++ 14:19:04 paras333: yeah, we need to make sure if asked question are blocking for further triage or not 14:19:17 I feel 1 or 2 weeks are a bit too short to close them. 14:19:30 true 14:19:54 bug reportee might not be so active in community or LP 14:20:04 no that's fine if there is an automated process and marking as incomplete wil take it cycle to close it then I am good 14:20:50 #topic Critical Reviews 14:21:09 any critical review 14:22:04 #topic Open Discussion 14:22:29 anything else to discuss today? 14:23:14 Just this one https://bugs.launchpad.net/tempest/+bug/1865276 , if you have time 14:23:14 Launchpad bug 1865276 in tempest "ssh.exec_command, exit_status not always properly reported?" [Undecided,In progress] - Assigned to Paras Babbar (pbabbar) 14:24:01 paras333: go ahead 14:24:09 this seems not valid right request right 14:24:27 we can have ssh command exec that won't return any output string 14:24:47 we can't just handle this as error 14:24:51 right? 14:25:31 paras333: ok, i have not checked the comment yet. is it on bug etherpad ? 14:26:04 Ahh , it's not high priority but yes I can add it to the bug to discuss list 14:26:49 ++ 14:27:03 yeah, please add, that will be helpful 14:27:11 anything else ? 14:27:32 thanks everyone for joining. 14:27:34 #endmeeting