09:00:33 #startmeeting qa 09:00:34 Meeting started Thu Sep 6 09:00:33 2018 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:36 PING LIST- gmann, andreaf, masayukig, chandankumar, felipemonteiro, frickler, mbindlish 09:00:37 The meeting name has been set to 'qa' 09:00:41 o/ 09:00:43 who all here today 09:00:46 masayukig: hi 09:00:48 hi 09:00:59 mbindlish: hi 09:01:12 * tosky more or less around 09:01:33 let's start 09:01:38 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_next_Office_hours 09:01:45 today agenda ^^ 09:03:13 #topic Announcement and Action Item (Optional) 09:03:26 Rocky is released for all QA projects 09:03:35 #link http://lists.openstack.org/pipermail/openstack-dev/2018-August/133636.html 09:03:42 devstack and grenade also done. 09:03:56 last patch for grenade setting to test Rocky upgrade is still not merged 09:04:02 #link https://review.openstack.org/#/c/591594/ 09:04:34 this is still failing. previous failure was due to osc which is fixed and released now 09:05:03 #link https://review.openstack.org/#/c/599924/ 09:05:15 i will check the current failure after meeting 09:05:28 #topic Rocky Priority Items progress 09:05:52 #link https://etherpad.openstack.org/p/qa-rocky-priorities-tracking 09:06:15 we finished most of the item but still few remaining 09:06:37 which i will put as backlog of Rocky in PTG and carry forward in stein. 09:06:42 great 09:07:05 we will see how much % we completed during PTG 09:07:47 anything else on Rocky priority ? 09:08:18 maybe not 09:08:27 ok let's move next 09:08:38 #topic OpenStack Events Updates and Planning 09:08:52 Next: Denver PTG 09:09:11 Denver PTG is next week, hope all set for travel 09:09:54 I have prepared the scheduled for QA 09:10:07 #link http://lists.openstack.org/pipermail/openstack-dev/2018-September/134279.html 09:10:10 yeah, thanks 09:10:17 #link https://etherpad.openstack.org/p/qa-stein-ptg 09:10:28 #link Ethercal: https://ethercalc.openstack.org/Stein-PTG-QA-Schedule 09:11:06 Basically Monday will be help hours and Tuesday - Thursday will be QA specific discussion 09:11:33 i have added the topic schedule on ethercal, please check and let me know if anything conflicting with other sessions. we can adjust that 09:11:46 also feel free to propose any other topic which you want to discuss 09:12:19 thanks, sure 09:12:34 ll check it 09:13:01 with current schedule we will finish our discussion on Wed first half. 09:13:18 i have planned Bug Triage and then Code sprint after that 09:13:29 ++ 09:14:11 we will plan QA dinner also in PTG which i will send mail separately. 09:14:39 +1000 :) 09:14:48 and we have Team Photo slot also on Wednesday 10.40-10.50 which i will coordinate during PTG 09:14:49 :) 09:14:51 masayukig: :) 09:15:20 that's all from my side on PTG planning. anything else on this 09:15:44 gmann: so, 09:16:21 I think operators will come to the PTG this time? 09:16:35 yes 09:16:43 gmann: so, maybe, we can get some feedback from them? 09:17:04 masayukig: nice idea. i can plan for that. 09:17:16 gmann: nice :) 09:17:19 any specific day for operator ? 09:17:31 no idea... 09:17:54 there is a room booked for "ops meetup" on Monday and Tuesday 09:18:16 yeah. Aspen 09:18:19 #link https://www.openstack.org/ptg/#tab_schedule 09:18:22 tosky: thanks 09:18:38 Monday is good time to check with them. 09:18:47 yeah 09:19:16 added in Ethercal for Monday 09:20:22 thanks! 09:21:07 let's move next 09:21:09 Next: Berlin Summit 09:21:26 I created the etherpad for QA Forum Sessions Brainstorming 09:21:42 #link https://etherpad.openstack.org/p/berlin-stein-forum-qa-brainstorming 09:21:54 #link http://lists.openstack.org/pipermail/openstack-dev/2018-September/134353.html 09:21:59 sent email ^^ also 09:22:14 let's start gathering the Forum ideas we can propose for QA related stuff 09:22:31 I think deadline is Sept 12th to collect the ideas 09:22:45 ooh, during the PTG 09:22:55 #link https://wiki.openstack.org/wiki/Forum/Berlin2018 09:23:39 #link http://lists.openstack.org/pipermail/openstack-dev/2018-September/134336.html 09:23:47 its Sept 11th actually 09:24:02 masayukig: yeah both things going in overlap way :) 09:26:00 gmann: ok, I'll check and we can talk about it at the PTG :) 09:26:15 yeah, PTG is also good time to talk 09:26:26 let me add it somewhere as reminder 09:27:25 added in ethercal. 09:27:59 cool 09:28:03 one things we should fill before Tuesday is Retrospective etherpad 09:28:17 #link http://lists.openstack.org/pipermail/openstack-dev/2018-September/134274.html 09:28:32 #link https://etherpad.openstack.org/p/qa-rocky-retrospective 09:28:43 feedback is much needed to improve the things. 09:29:38 this was my first cycle as PTL, so i love to hear the improving area so that we can take care more in Stein. 09:30:00 yeah, thanks. I'll do that. 09:30:04 gmann: :) 09:30:32 +1 09:30:38 thanks 09:30:42 #topic Sub Teams highlights (Sub Teams means individual projects under QA program) 09:31:13 Tempest 09:31:25 #link https://review.openstack.org/#/q/project:openstack/tempest+status:open 09:31:42 this is ^^ ongoing review in Tempest. 09:31:57 i do not have much extra to discuss now for Tempest 09:32:13 anyone have anything ? 09:32:42 I don't either 09:33:32 k let's move 09:33:34 Patrole 09:33:47 zhufl proposed openstack/tempest master: Remove unnecessary response check in InstanceUsageAuditLogTestJSON https://review.openstack.org/600394 09:33:59 there is one ongoing item i want to share here for patrole 09:34:22 #li k https://review.openstack.org/#/c/599488/1 09:34:25 #link https://review.openstack.org/#/c/599488/1 09:34:37 patrole is migrating to stroyboard. 09:35:00 before updating the link in README etc we need to migrate the bugs from LP to Storyboard. 09:35:38 once that is done, we will close the LP for patrole and completely moving to storyboard. 09:36:03 and in PTG we can discuss about it and talk about other QA project to migrate slowly. 09:36:29 k 09:37:32 anything else on subteam updates. ? i have nothing else 09:38:44 #topic Bug Triage 09:38:58 i will skip this and do more work on this in PTG 09:39:12 #topic Open Discussion 09:39:29 tosky: i saw your msg but sorry could not get time to look into your patch 09:39:40 gmann: oh, which message? Grenade? 09:39:45 yeah 09:40:06 I moved forward more or less, and I refined my question a bit 09:40:50 so: if the scope of grenade to verify only that configuration from $version-1 still works with $version, but not that it will work for $version+1 ? 09:40:57 ? 09:41:21 because otherwise it's impossible to *not* consider deprecated and removed options (which can happen in two cycles) 09:41:53 so the thing called fast forward upgrade or something like that is out of scope? 09:42:14 it does with master and master-1 also. and yeah version-1 to version if configured that way 09:42:38 yeah that is out of scope as far as i know. 09:42:38 right, master and master-1 (aka last stable) is a special case of version and verson-1 09:42:46 yeah. 09:42:47 ok, because that simplifies some assumptions 09:43:29 basically we switched to WSGI by default in Sahara, so what I did so far is force non-wsgi still for queens->rocky; rocky will deploy with wsgi directly 09:43:46 k 09:44:23 and that worked right 09:44:27 yes 09:44:37 cool 09:44:43 I found out a weird thing though; it seems that, if you use devstack plugin, you need to specify *again* the version they want to use as base and target 09:45:07 and that can go quickly unaligned with the base and target used by grenade in the same branch 09:45:43 see http://git.openstack.org/cgit/openstack/sahara/tree/devstack/upgrade/settings#n10 09:45:46 but that is set by d-g based on grenade branch - 09:46:14 that's what I thought, but if I don't see that on the plugin, apparently I get sahara and heat (in this case) from master also in old/ 09:46:41 unless I misread the logs 09:47:00 same here: http://git.openstack.org/cgit/openstack/manila/tree/devstack/upgrade/settings 09:47:08 #link https://github.com/openstack-infra/devstack-gate/blob/master/devstack-vm-gate-wrap.sh#L280 09:47:25 humm 09:47:38 but that's not what grenade writes in the devstack configuration file 09:48:04 if you use devstack_localrc base , that content will be written directly to the devstack configuration file 09:48:27 maybe it's as easy as making sure that devstack_localrc checks for enable_plugin directives and fills them properly 09:48:35 or maybe I don't know 09:48:59 #link http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/devstack-vm-gate.sh#n673 09:49:06 I did my testing with this patch (now abandoned) removing the version from enable_plugin and I noticed that sahara and heat were from master 09:49:21 ohk 09:49:21 https://review.openstack.org/#/c/599542/ 09:49:46 see http://logs.openstack.org/42/599542/1/check/sahara-grenade/a434859/logs/grenade.sh.txt.gz#_2018-09-04_09_53_26_125 09:49:54 so maybe I misread that, but... not sure 09:50:33 or maybe it's enable_plugin in devstack that should be fixed 09:52:16 seems so. 09:52:40 dansmith: can quickly update on this if we are missing anything ^^ 09:53:09 ok, I mean, a solution can be found, I just needed to double check and see what could be the "right" solution 09:53:21 who are the reference contacts for grenade these days? 09:53:36 yeah, i feel plugin should not needed to set the branches but not 100% sure 09:53:53 you can contact dansmith and he will be in your TZ. 09:53:55 not by default at least 09:54:27 thanks 09:55:01 anything else to discuss for today or we close the office hour. 09:55:09 nothing else from me 09:55:24 nope 09:55:29 one update nd lls end mail too. we will cancel the next week office hour due to PTG 09:55:36 and resume right after PTG week. 09:55:46 yeah 09:56:02 ok, thanks everyone for joining. have a safe travel and see u in Denver. 09:56:34 #endmeeting