13:30:54 #startmeeting qa 13:30:55 Meeting started Tue Apr 7 13:30:54 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:56 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:30:58 The meeting name has been set to 'qa' 13:30:59 who all here today ? 13:31:08 hello 13:31:17 hello 13:32:12 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting 13:32:44 agenda for today, we will try to finish today office hour fast due to m-3 things to complete 13:32:56 #topic Announcement and Action Item (Optional) 13:33:15 one announcement - welcome kopecmartin to the core team. 13:33:24 gmann: thank you 13:33:42 kopecmartin: congrats 13:34:51 #topic OpenStack Events Updates and Planning 13:35:07 as you all might know, we are going to have Virutal PTG. 13:35:27 I will plan the same for QA also based on topics we want to discuss. 13:35:39 please add your topic to discuss in this etherpad - https://etherpad.openstack.org/p/qa-victoria-ptg 13:36:14 kopecmartin: or soniya29 you can write the scenario manager things here and we can discuss that 13:36:26 sure, we'll do 13:36:38 gmann: sure. we will 13:36:41 or any other topic. like cleanup cli to move to main jobs in gate 13:37:04 thanks. and based on that we will plan the total time etc 13:37:27 #topic Sub Teams highlights (Sub Teams means individual projects under QA program) 13:37:32 Tempest 13:38:08 there is stein gate issue for tempest-full i have not looked into yet. we will check that in bug topic 13:38:11 Patrole 13:38:39 I think patrole gate is up but i have merged many policy on nova side so it might be broken. I will check and fix after m-3 13:38:43 Grenade 13:39:10 I need to re-review the zuulv3 jobs. again after m-3 13:39:35 anything else on team highlights ? 13:40:21 jumping to bugs things. 13:40:24 #topic Bug Triage 13:40:51 kopecmartin: go ahead 13:41:14 we have quite many patches to review , i put them in the etherpad 13:41:20 #link https://etherpad.openstack.org/p/qa-bug-triage-ussuri 13:41:46 most of the high priority ones are quite simple, so if you have some time, please, have a look 13:42:13 the bug numbers are still decreasing, which is great news 13:42:22 great, 13:42:40 i will be able to start review after m-3 which is friday this week 13:42:54 this is bug i was talking about for stein gate 13:42:58 #link https://bugs.launchpad.net/tempest/+bug/1871327 13:42:59 Launchpad bug 1871327 in tempest "stable/stein tempest-full job fails with "tempest requires Python '>=3.6' but the running Python is 2.7.17"" [Undecided,New] 13:43:29 not sure why tempest-full even it is py2 job not using the py3 venv on stein. I will this today if get time 13:44:04 all the job using master tempest and have py3.6 on system should use the same in their venv irrespective of they are py2 or py3 job 13:44:40 kopecmartin: any other critical gate blocking bug ? 13:44:43 ack 13:45:10 gmann: no 13:45:24 ok 13:45:28 #topic Critical Reviews 13:45:33 any critical review ? 13:45:46 critical no 13:45:54 just those mentioned in the etherpad 13:46:05 ok. 13:46:07 #topic Open Discussion 13:46:19 I added one topic there 13:46:36 Cleanup the QA project for non-active members 13:47:09 I saw there are many sub projects still has members in core list who are not active or not working in openstack any more. I will cleanup those. 13:47:33 how many projects are we talking about? 13:47:46 #action gmann to cleanup the QA sub projects core list. 13:48:03 kopecmartin: i have to check like bashate is one example 13:48:14 ah ok 13:48:20 hacking is another 13:48:28 next is - Volunteer for 'Hacking's maintainer. 13:48:52 I need to check how many attention it would require 13:49:03 we need volunteer if someone can stepup for hacking projects. we usually maintain it as traffic is less 13:49:23 but having few active in core list will be good. I will keep doing in that 13:49:25 re: grenade, just in case: we should be good hopefully: tempest logs are captured, branches are defined in a single role (even though it's called twice) 13:49:50 tosky: thanks for update. I will check it after m-3 13:50:09 twice is ok, we can optimize the job later and let's get the base stuff working in 13:50:58 any other topic to discuss today ? 13:51:11 Do we support windows instance to be used with tempest test? 13:51:52 as long as nova is configure with hyperV and all it should. 13:51:55 and image etc 13:52:21 I mean I know some may take more than 300 secs to be available with volume backed and all and saw some issues there so 13:52:22 there is no specific dependency of Tempest on instance type 13:52:51 from Tempest side issue or env not booting instance ? 13:53:42 it takes sometime more than 300 sec to boot with virtual size of windows image is more than 40 GB as that require 40 GB volume as well to attach 13:53:57 so I have seen timeout issue appearing 13:54:07 from the waiters 13:54:18 did you check nova logs ? 13:54:31 40 GB wow 13:54:46 yup doing it without tempest worked fine 13:54:56 like manually running it 13:55:18 anyways I will share the logs if it support, thanks! 13:55:19 it can be test timeout or service side timeout. 13:55:23 cool 13:55:57 there is HyperV CI on nove gate which run tempest on window VM so it work for sue 13:55:58 sure 13:56:10 but that large config, i am not sure. 13:56:17 anything else? 13:56:23 gmann: ack 13:57:00 ok let's close for today 13:57:04 thanks everyone for joining 13:58:31 #endmeeting