13:32:08 #startmeeting qa 13:32:09 Meeting started Tue Mar 17 13:32:08 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:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:32:13 The meeting name has been set to 'qa' 13:32:16 who all here today? 13:32:26 \o/ 13:34:23 kopecmartin: seems two of us. 13:34:36 yeah 13:34:36 three 13:34:46 rh-jelabarre: hi 13:35:07 hi 13:35:15 gmann: hey Gm! 13:35:18 hi 13:35:21 let's start 13:35:32 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours 13:35:38 ^^ today agenda 13:36:59 #topic Announcement and Action Item (Optional) 13:37:34 no AI from previous meeting 13:37:55 #topic Ussuri Priority Items progress 13:38:08 #link https://etherpad.openstack.org/p/qa-ussuri-priority 13:39:03 Remove/migrate the .testr.conf to .stestr - masayukig 13:39:26 Lee Yarwood proposed openstack/devstack-plugin-ceph master: Updates script to use latest version of Ceph https://review.opendev.org/676722 13:39:34 i did not see patches for this, will wait for masayukig response. 13:39:40 Liang Fang proposed openstack/devstack-plugin-open-cas master: Initial repo https://review.opendev.org/713173 13:40:21 py2.7 drop plan for QA - gmann 13:40:48 this is almost done for all QA projects. and i released few of the tools. 13:40:55 I will do audit for those and mark complete 13:41:10 new whitebox plugin for tempest 13:41:47 this is +2 from me. may be masayukig can re-review this - https://review.opendev.org/#/c/656890/ 13:42:05 Improving Tempest cleanup: mkopec 13:42:17 i think i have not reviewed that ? 13:42:30 this is still ongoing, we have a few patches to review 13:42:50 yeah, there's a new patch by Lukas (he's no here atm) 13:43:07 kopecmartin: ok, can you add those with single topic 13:43:17 sure 13:43:25 thanks 13:43:46 #topic OpenStack Events Updates and Planning 13:43:59 Vancouver Summit & PTG 13:44:56 As you all might have seen the ML thread that OSF still deciding the June event whether to do virtually or physically. 13:45:44 also as per expected attandance for QA, i have marked QA as runtime booking of space in PTG if we have physical PTG and any of us attend that. 13:46:17 otherwise I will think on holding it virtually. sometime during May or April end 13:46:44 #topic Sub Teams highlights (Sub Teams means individual projects under QA program) 13:46:49 Tempest 13:47:07 #link https://review.opendev.org/#/q/project:openstack/tempest+status:open 13:47:14 these are open request 13:47:30 other than that no specific update form me. 13:47:34 anyone ? 13:48:12 Added patch yesterday https://review.opendev.org/#/c/713151/ for this old bug https://launchpad.net/bugs/1676207 13:48:13 Launchpad bug 1676207 in tempest "test_create_router_set_gateway_with_fixed_ip is flaky" [Low,In progress] - Assigned to Paras Babbar (pbabbar) 13:48:40 gmann: it will be great if you can review, it was among the high importance bug we discuss last time 13:48:42 paras333: thanks. 13:49:14 is it on bug etherpad ? 13:49:20 paras333: imp seems low in LP 13:49:29 anyways we will discuss on bug topic 13:49:44 ok 13:49:55 Patrole 13:50:14 gate is broken for Patrole. with my change in nova policies 13:50:25 i am fixing here #link https://review.opendev.org/#/c/711367/ 13:50:36 seems i need to fix reno 13:50:51 other that that no major updates from patrole 13:51:18 grenade 13:51:44 ironic grenade job on stein was broken due to Tempest constraint 13:51:51 it is fixed and working now- #link https://review.opendev.org/#/c/713014/ 13:52:31 I had to use stable constraint for old node tempest run for stein job also. old node in stein is rocky which has Tempest pinned. 13:52:50 this we might need to do on every release move to EM 13:52:53 grenade: I need to complete the requested fixes for the zuulv3 jobs, I was driven away by other duties; hopefully I will upload a new version before the end of the week 13:53:08 or when we cap the Tempest on any stable branch 13:53:26 tosky: thanks for that. i was about to ask that. 13:53:36 sounds good. take your time 13:54:27 anyting else on any other project ? 13:55:17 one update is openstack-heath nodejs job is udpated to 10 LTS #link https://review.opendev.org/#/c/711380/ 13:55:36 thanks to vishalmanchanda to fixing it and making gate green. 13:55:59 #topic Community goal tracking 13:56:29 py2 drop we already discussed. contributor guide role is not started yet. 13:56:46 #topic Bug Triage 13:56:50 kopecmartin: soniya29 go ahead 13:57:27 very lacking core reviews , we should gain attention a little more if possible 13:57:49 ok, patches listed on etherpad right ? 13:57:58 there is plenty of fixes ready for reviews, listed in the etherpad 13:57:58 yes 13:58:13 and some of them are there for weeks 13:58:26 ok, I started burning the volume json schema things last week which are pending for long time. 13:58:42 I will check etherpad one also this week 13:58:49 yeah, i've seen some reviews regarding the json schema in general 13:59:08 i was about to review them for some time .. I will reserve time for that too 13:59:23 cool thanks 13:59:26 https://bugs.launchpad.net/tempest/+bug/1866270 13:59:27 Launchpad bug 1866270 in tempest "CI job 'grenade-py3' broken" [Undecided,New] 13:59:42 "how do we deal with CI failures related bugs? it's not tempest's fault, it's infra, where should we redirect these bugs? " 13:59:55 is it job issue ? or infra 14:00:21 i think infra, let me check 14:00:33 yeah, a host was not found .. 14:00:41 seems like scheduler was not able to find a host 14:00:43 so yes infra 14:01:32 i mean it is compute side issue which can be due to various reason 14:01:59 i see, so should we change the project to compute? 14:02:07 in those cases, we need to comment and mark invalid for Tempest/grenade and open for that project 14:02:25 we need more info on that. I will comment on that 14:02:29 very less logs here to say 14:02:40 https://bugs.launchpad.net/tempest/+bug/1863161 14:02:42 Launchpad bug 1863161 in tempest "stackviz failing on stable jobs with py3.5 while installation" [Undecided,In progress] - Assigned to Ghanshyam Mann (ghanshyammann) 14:03:16 stackviz is fixed for py3.5 but i think i had Tempest patch also not to fail job for any failure in stackviz 14:03:24 i will check if that is not merged yet. 14:03:53 3.5 is dropped form Tempest but we restored its support in stackviz as rocky job still use py3.5 on their xenail node 14:03:56 xenial 14:04:22 so till rocky is EOl we can keep supporting it. pinning stackviz is too complex 14:05:56 https://bugs.launchpad.net/tempest/+bug/1783405 14:05:57 Launchpad bug 1783405 in tempest "Slow tests randomly timing out jobs (which aren't marked slow)" [High,In progress] - Assigned to Ghanshyam Mann (ghanshyammann) 14:06:47 this is something we keep monitoring and if we find the slow test then we mark it slow. we did complete first phase of this but I will say to keep it open for ussuri cycle in case we find more slow tests. 14:07:23 ah, ok , good to know 14:07:37 ack 14:07:44 commented on LP also 14:07:48 any other bug to discuss ? 14:07:53 paras333: your ? 14:08:06 I added that in etherpad 14:08:51 for the record: https://launchpad.net/bugs/1676207 14:08:52 Launchpad bug 1676207 in tempest "test_create_router_set_gateway_with_fixed_ip is flaky" [Low,In progress] - Assigned to Paras Babbar (pbabbar) 14:08:53 link 14:09:04 https://review.opendev.org/#/c/713151/ 14:09:42 background: there's a question on how to obtain fixed ips without a race condition 14:10:15 yeah so the only suggestion I thought is to create the external network and use that for the fixed IP 14:10:40 what is frequency of this ? 14:10:48 rather than using the network id which is shared among many other tests as that's what causing the race 14:10:49 is it happening on gate too ? 14:11:03 yeah, dedicated network will be good approach here. 14:11:14 I see it is open from 2017 and people have seen this a lot and then we put the skip flag like 3 years ago 14:11:25 not that big frequency nowadays, that's why we decreased priority , but if we can solve, i'd do it 14:11:27 anyways. I will add this in e-r if not yet there and see what is occurance 14:11:52 yeah, we can get paras333 fix in parallel. 14:12:13 I will review that in this week or today if find time 14:12:19 thanks 14:12:26 thanks guys!! 14:12:27 anything else on bug side ? 14:12:34 not from my side 14:13:03 nothing else!! 14:13:19 kopecmartin: what you think on maintaining the critical or High importance bugs section also in report so that we triage/fix/review them on priority. 14:13:40 critical is 0 but i see 6-7 high priority bug hanging without much attensions 14:14:00 section in etehrpad i mean 14:14:14 gmann: hmm, ok , let me increase the priority on the related bugs, i forgot i got those powers :) 14:14:55 kopecmartin: i mean priority you set as per triage policy or like frequency and imp of bugs as usualy. 14:15:20 i mean all High priority or critical merked bug in separate section on etherapd so that we keep checking them 14:15:30 oh, sure, no problem 14:15:32 i'll do it 14:15:36 gmann: yeah I like the idea 14:15:44 i'll divide them into two sections, makes sense 14:16:05 thanks. because our main idea is to fix critical the high priority first and then rest all 14:16:45 and i will say good progress on bug things, it has decreased a lot 14:16:56 #topic Critical Reviews 14:17:16 any critical review ? 14:17:32 gmann, in other news, tripleo ci team has moved almost all the jobs to centos-8 running py3 14:17:40 *tripleo jobs 14:18:18 chandankumar: great. 14:18:37 i think few of the projects like kolla were waiting for that 14:19:11 not sure if that can help ansible modules also which still running centos7. few of my py2 cleanup patches failing on that job 14:19:19 gmann, if something got missed, we get it done 14:19:33 gmann, do you have job link? 14:19:37 +1 14:20:43 chandankumar: this one is one of it- #link https://review.opendev.org/#/c/710680/ 14:21:16 gmann, thanks, adding to my list 14:21:23 thanks 14:21:25 #topic Open Discussion 14:21:41 anything else to discuss ? 14:23:00 ok, let's close for today. thanks everyone for jojning 14:23:03 gmann: just a heads up I'm planning a new stestr release in the next month 14:23:13 it'll drop support for python 2 14:23:17 mtreinish: ok. 14:24:03 mtreinish: i think almost all projects moved to py3 but we might need to check on swift which still running py2 jobs 14:24:16 they can use cap in that case 14:24:34 Mohammed Naser proposed openstack/devstack master: zuul: Added reference tenant configuration https://review.opendev.org/713454 14:24:42 mtreinish: will you add cap in g-r also ? for py2 version 14:25:23 I wasn't planning on it, but it might be necessary. I'll be setting a python requires for >=3.5 for the stestr 3.0.0 release so that might cause an issue on python2 if u-c says 3.0.0 14:25:37 gmann: https://github.com/mtreinish/stestr/pull/287 14:27:00 stable branches py2 cap to 2.0.0 i think but we can see if it break things on py2 jobs on ussuri onwards if any swift is known one 14:28:16 thanks for updates. 14:29:11 #endmeeting