09:00:21 #startmeeting qa 09:00:22 Meeting started Thu Dec 15 09:00:21 2016 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:00:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:25 The meeting name has been set to 'qa' 09:00:57 Hello, who's here today? 09:01:08 o/ 09:01:55 DavidPurcell: hi 09:02:10 let's wait for some time for more people to join 09:02:14 good morning :) 09:02:23 morning 09:02:50 masayukig: andreaf dmellado hi 09:03:12 o/ 09:03:15 o/ gmann morning 09:03:17 hi guys 09:03:41 morning 09:05:02 let's start 09:05:05 hi 09:05:15 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_December_15th_2016_.280900_UTC.29 09:05:25 ^^ Today's agenda 09:05:31 oomichi : oh, too early for you? 09:05:49 masayukig: I am in Japan now 09:05:57 oomichi: hi 09:06:06 oh, cool, I see :) 09:06:09 #topic Specs Reviews 09:06:24 #link https://review.openstack.org/#/q/status:open+project:openstack/qa-specs,n,z 09:06:46 most spec under review and waiting on author side 09:06:50 on this one - https://review.openstack.org/#/c/410250/ 09:07:13 oh, oomichi welcome back ;) 09:07:15 i did not get why we have to revert this instead of just updating if needed 09:07:41 gmann: yeah, I also cannot get the reason yet 09:07:57 but my point is policy.json cannot be removed immediately 09:08:01 I wasn't sure why they wanted a revert either. Do we know the timeline on the change they're making? 09:08:02 gmann: maybe he just wanted to get feedback more? 09:08:18 oomichi: may be 09:08:25 by reverting 09:08:48 DavidPurcell: well even they have merged i think older way still in support 09:09:21 I was thinking like go with current spec and if we need to adopt new middleware way then it can be done 09:09:42 gmann: yeah, I don't think we can remove the old(?) style soon 09:09:43 spec is just to make policy bits testing which way that can be done/changed there 09:09:53 I think the revert commit needs more explanation in the commit message at least. 09:10:18 masayukig: ++ 09:10:20 masayukig: yea, i asked few query on review let's wait for reply may be 09:10:45 to be honest, I really want to -2 because the commit message doesn't explain why 09:10:52 gmann: I like that approach. I think it should be reasonably easy to adapt tests from policy.json into tests for middleware once the new approach is released 09:10:53 yeah, it's not really clear at all why they'd like to put that up 09:11:05 I'll -1 it and ask for the commit message to be clarified 09:11:36 DavidPurcell: yea, thats how a testing tool should do actually 09:11:52 anyways let's wait for more clarity there 09:12:14 any other spec to discuss ? 09:12:19 gmann: yeah, nice direction 09:13:03 gmann: maybe my new spec will be abandoned soon 09:13:20 the decorator seems very small without spec enough 09:13:26 oomichi: which one? 09:13:32 #link https://review.openstack.org/#/c/405637/ 09:13:36 oomichi: yea 09:13:47 gmann: https://review.openstack.org/#/c/405637/ 09:13:55 * andreaf o/ 09:13:56 m +2 on abandon :) 09:13:57 gmann: yeah, that is 09:14:00 andreaf: hi 09:14:24 gmann: abondoned it now 09:14:28 oomichi: then should we just go ahead on the implementation without bp? 09:14:41 yes 09:14:41 dmellado: yeah, I am feeling it is 09:14:57 spec is too heavy for that :) 09:15:16 oomichi: did all patches ready before updating spec 09:15:32 gmann: yeah, I think so 09:15:51 gmann: and the implementation is already done with applying the comments, 09:15:58 +1 09:15:58 thanks all for the comments anyways :) 09:16:02 yea 09:16:25 m almost ok with that waiting for andreaf feedback on that 09:16:27 #link https://review.openstack.org/#/c/405781/ 09:16:46 anyways let's change topic and discuss this in Tempest 09:16:56 #topic Tempest 09:17:00 gmann: heh sorry I will check it after the meeting 09:17:10 andreaf: sure 09:17:17 andreaf: thanks 09:17:24 on tempest, gate is blocked now on liberty jobs 09:17:36 as liberty EOL and nova liberty branch no more and job fail 09:17:49 gmann: oh, I didnt know that 09:18:06 there are patches to remove the liberty job from tempest 09:18:08 #link https://review.openstack.org/#/c/410928/1 09:18:33 which is all together with other changes and other base patches also 09:18:37 this can take time to merge 09:18:38 gmann: nice picking up, I will review it soon 09:18:51 so i separately created another one 09:18:53 #link https://review.openstack.org/#/c/411113/ 09:19:08 ^^ this one, just remove tempest liberty jobs 09:19:25 but ok with any of them gets merged first 09:19:28 gmann : is that included in 410928? 09:19:36 pinged infra team on channel but still need reivew 09:19:49 masayukig: yes, but with all other cleanup 09:20:07 gmann: I'll get some infra attention on this, it'd be great to have it merged asap 09:20:14 it seems to be impression that no one runs liberty as voting job 09:20:25 yeah 09:20:43 dmellado: yea, i pinged all guys there just waiting for them to approve either patch 09:20:53 yeah, https://review.openstack.org/#/c/411113/ needs to be merged soon 09:21:43 yea 09:21:49 if liberty will no longer be tested in the gates 09:22:03 should we create a tag announcing that tempest will no longer support it? 09:22:31 I was going to ask the same, iirc tempest is tagged also when an openstack release is retired 09:22:32 dmellado: yeah good point 09:22:57 dmellado: yea nice point 09:23:12 oomichi: ^^ can you do ? 09:23:15 oomichi: I guess that's one for you :) 09:23:19 tosky: yeah, the tag should be added when each EOL 09:23:29 "PTL's work" 09:23:35 gmann: yeah, I will do that after removing jobs 09:23:50 #action oomichi needs to tag tempest on liberty EOL 09:23:52 oomichi: thanks 09:24:40 next is open review on tempest 09:24:42 #link https://review.openstack.org/#/q/project:openstack/tempest+status:open 09:25:18 as gate is blocked but we can keep doing +2, +1 may be :) 09:25:57 another thing on gate is puppet jobs also failing 09:25:59 or -1, -2 :-p 09:26:01 #link https://review.openstack.org/#/c/409670/ 09:26:07 hi (I am late sorry) 09:26:11 masayukig: yes thats always valid :) 09:26:11 hey jordanP 09:26:15 jordanP: hi 09:26:42 i pinged EmilienM on that, i suspect its due to liberty EOl only 09:27:23 gmann: puppet jobs are using liberty also? 09:27:34 gmann : I hope so 09:27:40 oomichi: not sure, from log i did not find out the reason actually 09:27:52 gmann: oh, OK 09:28:09 but i think they have some of the liberty branches using in their testi ng 09:28:43 if that's the case, they'd all broken too, yeah 09:29:12 let's wait for their finding 09:29:49 anything on tempest side more or we jump to bug 09:30:11 gmann: ++ for jumping to bug triage 09:30:19 ok 09:30:30 so this week dmellado your turn ? 09:30:32 #link https://etherpad.openstack.org/p/ocata-qa-bug-triage 09:30:37 yep, I'll take it over until next week 09:30:39 #link https://github.com/oomichi/bug-counter#current-graph 09:30:46 #link https://etherpad.openstack.org/p/tempest-weekly-bug-report 09:31:21 ah, I didn't update the graph this week. sorry about that: https://github.com/oomichi/bug-counter#current-graph 09:31:23 dmellado: oh, i thought this week, 8 - 15 09:31:28 andreaf: maybe you could update (in case you didn't do it last week) 09:31:51 gmann: chandankumar was assigned for that time in between 09:31:56 what about automatically closing very old bugs ? Like 2 years old ? 09:31:58 but he told me that he got somehow deleted 09:31:59 * gmann dates confuse always as those are end dates not start dates 09:32:11 dmellado: oomichi updated the graph I think 09:32:30 jordanP: yes we need some type of pruning like that 09:32:33 gmann: then I'm confused too 09:32:41 but not automatic closing, please 09:32:41 jordanP: +1 but after looking into those not just directly 09:32:57 tosky : ++ 09:33:00 most of them not be valid 09:33:02 was my turn this week then? I was expecting to do this from 15-22 09:33:09 dmellado: yea 09:33:20 yes, don't close bugs that still seems valid or bug with high priority, of course 09:33:22 * dmellado mistook the dates then 09:33:23 ok let's put date range there to avoid confusion 09:33:33 +1 for date range 09:33:51 #action gmann to add date range on bug triage etherpad 09:33:57 ++ 09:34:00 ++ 09:34:20 ok so we can skip this week until andreaf want to highlight any one bugs from last week 09:34:20 if that's the case I'll take a look with rodrigods too, but I'd say he thought the dates were different too 09:34:27 andreaf: you did lot of cleanup 09:34:52 new bug count is in single digit o/ 09:34:53 ah, this week report should be dmellado 09:35:13 gmann : \o/ cool! 09:35:14 oomichi: I mistook the dates and thought my turn was from today 'til next wed 09:35:16 andreaf has done already on the previous meeting 09:35:31 gmann: I mostly went through bugs in new state - some where old and not valid anymore - so I think jordanP has a point we need to do the same also for bugs in triaged and in progress state 09:35:50 +1 09:35:52 dmellado: ok, I put your name for the next meeting 09:35:58 oomichi: thanks! 09:36:08 dmellado: thank you also :) 09:36:09 and in progress we might need to open/close as many of the patches might be abandon 09:36:17 oomichi: but toally +1 for the date range, I mistook it xD 09:36:17 ok, so let's agree we can try to be more "aggressive" in closing bugs older than 2 years 09:36:23 one good news is that not the non-admin / test-accounts job are almost back to green - only one issue left with swift tests 09:36:35 jordanP : +++ 09:36:43 dmellado: yeah, it was easy to misread the etherpad 09:36:47 andreaf: great, you rocks :) 09:36:58 jordanP: ++, there should be quite the old bugs that are not even valid anymore 09:37:00 jordanP: if that the info command, or is there a "decision" meeting bot command? 09:37:06 I'll take a look and clean them up too 09:37:15 I didn't say to not close them, but just to at least read them before closing 09:37:17 jordanP: yea thats should be fine. 09:37:32 there could be a "bug re-triaging" session 09:37:33 tosky: maybe you'd like to join the cleanup these days :D 09:37:35 tosky : yes, of course, we should do that 09:37:36 tosky: yeah, that is good before closing 09:37:40 tosky: yea not close just by time after reading and ll be quick to close 09:37:40 well, I don't know about the meeting bot, I am not the chair here :) 09:37:56 let's make it an "info" :) 09:38:11 dmellado: if it's after the next two weeks, sure 09:38:18 #agreed we can try to be more "aggressive" in closing bugs older than 2 years 09:38:30 andreaf: thanks 09:38:45 only chair can do that I fear 09:38:55 gmann: so you have to do it if you want :D 09:39:05 https://github.com/openstack-infra/meetbot/blob/master/doc/Manual.txt#L138 09:39:07 again ? 09:39:18 yes 09:39:20 #agreed we can try to be more "aggressive" in closing bugs older than 2 years 09:39:24 I think mine is not taken into account 09:39:24 hah 09:39:28 heh 09:39:31 same :) 09:39:31 awesome 09:39:34 oups 09:40:02 nevermind I guess, let's move on maybe 09:40:06 yep 09:40:09 yea 09:40:14 ll check later 09:40:49 andreaf: on account job, v3 one is also done 09:41:20 gmann: I need a +W https://review.openstack.org/#/c/410677/ 09:42:06 andreaf: nice, +1 09:42:12 andreaf: thanks 09:42:18 andreaf: +1, added yolanda to have a look too 09:42:41 dmellado: yolanda is near by you ? 09:42:58 gmann: I was speaking with her just before the meeting, yeah 09:43:14 andreaf: is that voting job? 09:43:16 dmellado: can ask her to approve liberty job patches 09:43:24 gmann: I guess she already did 09:43:26 could you check? 09:43:29 oomichi: :) 09:43:52 oomichi: experimental only 09:43:54 dmellado: nice thanks 09:43:59 gmann: np 09:44:04 andreaf: ah, I got it 09:44:32 +1 09:44:49 btw, did you notice any failure with the ssh job ? 09:45:23 jordanP: it was all ok till noon i think 09:45:36 https://review.openstack.org/#/c/409670/ 09:45:40 jordanP : link? 09:46:03 no link, because no failure :) 09:46:09 I want the job to be voting 09:46:10 heh 09:46:18 that's why I am asking if it's stable 09:46:23 jordanP: big +1 09:46:38 may be we can do soon after health dashboard data of week or 2 09:46:39 jordanP: good point I need to check that 09:46:57 what do you prefer guys: 1) make it voting ? 2) reconfigure gate-tempest-dsvm-neutron-full-ubuntu-xenial so that it enabled ssh-validation ? 09:47:39 I tend to prefer 1) 09:47:40 only diff in both is ssh only right 09:47:47 I'd take 1) as it'd be cool to have both of them just in case 09:47:57 yea 1 make sense 09:48:11 both would not be good, we can keep 1 i think 09:48:12 it seems easy to distinguish different factor 09:48:34 ok 09:48:40 yaeh, so agreed on 1) them? :D 09:48:51 oh sorry 09:48:56 gmann: you can use the agreed command again :D 09:49:00 i was on 2 side if only diff is ssh 09:49:16 after agree :) 09:49:18 gmann: heh ok not yet 09:49:45 if both same then we can make only single job 09:50:01 who want to check that 09:50:09 (I prefer 2 myself) 09:50:12 I'll check 09:50:16 jordanP: me too 09:50:20 jordanP: thanks 09:50:26 jordanP: gmann: how about keeping both of them and drop after we're sure that it's stable 09:50:26 we already have a big number of jobs 09:50:41 if you're safe on that, then I don't really mind but I'll wait a bit 09:50:52 #link http://status.openstack.org/openstack-health/#/g/build_name/periodic-tempest-dsvm-neutron-full-ssh-master 09:50:58 we can take a small risk, given it will be easy to revert 09:50:59 #action jordanP to check diff between neutron jobs and ssh one 09:51:15 andreaf: thanks 09:51:41 andreaf, thanks. So stable for the last 7 days, which is good 09:51:48 after 5 its looks stable 09:51:58 thanks to andreaf's work 09:52:10 yea, nice work andreaf 09:52:13 yeah 09:52:25 ok, only 8 min left 09:52:32 let;s move to next 09:52:34 it was a lot of contributions from the team to make that job stable 09:52:41 we can skip devstack if nothing on that 09:52:52 +1 on skip from my side 09:53:12 ok 09:53:21 #topic openstack-health 09:53:30 #link https://review.openstack.org/#/q/project:openstack/openstack-health+status:open 09:53:37 masayukig: your turn 09:53:40 I encourage tempest reviewers to also review devstack changes, it's really informative 09:53:47 gmann : yeah, 09:53:50 jordanP: +1 09:53:54 jordanP: +1 09:54:19 yeah, totally 09:54:34 #agreed tempest reviewers to also review devstack changes, it's really informative 09:54:35 jordanP : ++ 09:54:40 heh 09:54:43 :( 09:54:50 o-h: only one graph fix patch was approved, and there are some tiny fixing patches are there, but I think it's not so much active these week. 09:55:09 not only devstack, all core projects ;) 09:55:11 openstack=health is getting quite nice, it's faster now, and the user feedback and the graphs are nicer 09:55:19 so good job on that! 09:55:30 very nice. 09:55:32 andreaf : !!! :) 09:55:50 yeah, it is easy to know the situation of all projects 09:56:00 that's it from my side. 09:56:10 4 min 09:56:23 masayukig: ok, thanks for your hardwork on that 09:56:30 #topic Critical Reviews 09:56:39 any critical reviews on priority 09:57:31 ok, may be once gate is open :) 09:57:36 heh 09:57:39 :) 09:57:56 please check mine then 09:57:58 #link https://review.openstack.org/#/c/409634/ 09:58:01 and dependent one 09:58:25 one note from my side - a few periodic jobs have been renamed - the node type is not in the name (ubuntu-xenial) so you have to include that in case you had some bookmark 09:58:25 after object client to lib we can finish all service cleints 09:58:42 andreaf: nice thanks 09:58:45 gmann: yay 09:58:49 yeah, we should focus on finishing the migration 09:58:53 #info a few periodic jobs have been renamed - the node type is not in the name (ubuntu-xenial) so you have to include that in case you had some bookmark 09:58:58 andreaf: so now avery node would be just ubuntu-xenial 09:58:59 jordanP: yea 09:59:05 and it's just not explicitly marked, isn't it? 09:59:06 we are almost there 09:59:11 yea 09:59:18 let;s jupo to open 09:59:25 #topic Open Discussion 09:59:31 when is the right time to restart the disussion (pike) about always splitting tempest plugins (https://review.openstack.org/#/c/369749/) ? 09:59:46 tosky: that's a good question too 10:00:00 tosky: may be in feb starting 10:00:10 1 min left 10:00:15 just before the PTG, although I'm pretty sure we'll have to bring 10:00:18 the cross-project session again 10:00:32 * masayukig nods 10:00:37 Speaking of splitting plugins, project for RBAC plugin is awaiting governance 10:00:37 ok thanks all, let's move to qa for further discussion if any 10:00:46 #endmeeting