09:01:13 #startmeeting qa 09:01:14 Meeting started Thu Jan 26 09:01:13 2017 UTC and is due to finish in 60 minutes. The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 09:01:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:01:17 The meeting name has been set to 'qa' 09:01:29 hi, who all here today 09:01:42 me:) 09:01:57 o/ 09:01:58 o/ hey gmann 09:02:11 dmellado: hi 09:02:22 zhufl: nice, thanks. 09:02:50 Hello guys! 09:02:55 hey chandankumar! 09:03:01 chandankumar: hi, nice to see you 09:03:07 btw gmann, we should change the email to say CET and not CEST anymore 09:03:10 chandankumar zhufl dmellado hi! 09:03:14 I was about to miss the meeting because of that! 09:03:15 o/ hi everyone, first time here :) 09:03:18 hey masayukig!!! 09:03:25 gitudaniel : welcome!! 09:03:26 hi 09:03:27 welcome gitudaniel 09:03:29 gitudaniel: hi welcome 09:03:34 Noam_: hi 09:03:37 first time here also 09:03:40 masayukig: gitudaniel gmann Hello 09:03:42 welcome too ;) 09:03:52 dmellado: ah, ok ll change its all confusing to me always :) 09:04:03 let's start 09:04:04 gmann: it'd be CET 10:00 09:04:05 * masayukig is surprised that there are a lot of people this time 09:04:05 xD 09:04:16 masayukig: heh xD 09:04:19 #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Agenda_for_January_26th_2017_.280900_UTC.29 09:04:34 ^^ agenda 09:04:48 #topic PTG 09:05:07 #link https://etherpad.openstack.org/p/qa-ptg-pike 09:05:12 dmellado: :) 09:05:16 so this is etherpad for QA PTG 09:05:31 lot of topic this time 09:05:36 it is actually nice 09:05:46 if anyone have more feel free to add 09:06:16 gmann : cool :) 09:06:16 who owns the first one? infra team? 09:06:27 gmann: just one question, can anyone attend ptg virtually also? 09:06:53 chandankumar: ah, i am not sure there are such arrangement 09:06:59 #link http://lists.openstack.org/pipermail/openstack-dev/2017-January/110909.html 09:07:00 dmellado: the next PTL? 09:07:08 ^^ this says some tooling for PTG 09:07:23 I have one question, how many slots do we have? 09:07:28 masayukig: maybe 09:07:31 that's a goof question 09:07:40 gmann: well, we can always be active at the IRC and etherpads 09:07:42 dmellado: yea i think clarkb gave idea and we can discuss in PTG 09:07:57 great 09:08:01 masayukig: this time no slot, its just room book for full 2 days 09:08:02 I don't see why can't we allow virtual attendees (on best effort, though) 09:08:07 good idea 09:08:13 chandankumar: you cannot join? 09:08:22 gmann: till now not sure! 09:08:44 we can allocate the group there around tables and work on each items 09:09:02 chandankumar: ohhk 09:09:06 * dmellado trying to make that happen 09:09:13 gmann: hrmm, I think we should make time slots 09:09:15 dmellado: great +1 09:09:36 otherwise, it will be an endless discussion :-p 09:09:45 heh +1 masayukig 09:09:55 masayukig: so discuss can be with all attendee right 09:10:21 gmann: masayukig maybe we can discuss that there 09:10:25 masayukig: dmellado i saw a mail on those arrangement, i think oomichi also send 09:10:33 after seeing the final attendees and the amount of people interested on each topic 09:10:38 dmellado: i feel better to prepare before going 09:10:55 gmann: we can use the etherpad for that too 09:11:00 dmellado, gmann : ok, cool 09:11:03 we have only 2 days and topics are more this time so we have to plan well before 09:11:05 how about adding a new section 09:11:09 interested: 09:11:09 dmellado: yea 09:11:11 or something 09:11:20 gmann +1 09:11:30 chandankumar: that way you'l be also able to add yourself there too 09:11:54 #link http://lists.openstack.org/pipermail/openstack-dev/2017-January/110985.html 09:12:10 dmellado: nice idea, we can add that 09:12:13 * chandankumar added a field coowner on etherpad 09:12:29 #action add interested section on PTG topics 09:12:48 so above mail is for discussion how arrangement will be there in PTG 09:13:39 but many of them are more towards coding side so that people can just start making group on interested one and contribute 09:13:47 like tempest-lib, cleanup etc 09:14:31 so we can divide like groups working on those and in parallel discussion on other topic 09:14:40 gmann: will it be like an mid-cycle meetup? 09:15:03 but we should not overlap the discussion topics where many people want to join all discussion 09:15:19 masayukig: i think mid-cycle + design sessions 09:15:23 gmann: masayukig I was also thinking about how to organize the 'session' topics 09:15:32 is there any idea for having actual slots? 09:15:38 I'm thinking about the plugin talk 09:15:40 gmann : ok 09:15:53 sessions need broader discussion, we can go like we used to do in design sessions 09:16:20 and sessions more on just coding side can go like we used to have in mid-cycle 09:16:28 +1 09:16:36 +1 09:16:36 dmellado: you mean cross project one like? 09:16:43 yeah, exactly 09:17:05 I'll be re-doing the plugin one, in order to summarize the discussion on the TC proposal 09:17:18 mtreinish: ^^ would you like to co-present that with me too? 09:17:23 dmellado: that is nice point and not sure how that will go as very few people from other projects might show on first 2 days 09:17:25 gmann: dmellado we might need cross project discussion for tempest plugin side 09:17:41 chandankumar: yeah, that's what I was thinking out loud 09:17:41 chandankumar: yea 09:18:08 IT would be also good if we get one member from each openstack project to participate so that they can start spliting tempest plugins 09:18:31 chandankumar: well, I guess the talk would be a mean for that 09:18:32 dmellado: did you add all related projects in "Interaction with another project" 09:18:42 the TC proposal have yet to be accepted 09:18:48 based on that we can ask projects representative for those sessions 09:18:50 gmann: I guess I'd just say *all* 09:19:02 I mean, that'd affect every project that has an in-tree tempest plugin 09:19:10 I'll try to put out a list later on 09:19:16 andreaf: didn't you already had one around? 09:19:16 chandankumar: that is perfect one but we do not have members from all projects :) 09:20:26 dmellado: have so many contacts, he can find out representative xD 09:20:34 heh xD 09:20:37 but i doubt members from vertical teams will show up in mon and Tues 09:20:55 gmann: I can try to bring along at least some folks, deff 09:20:57 yea he is all rounder 09:21:00 heh 09:21:08 dmellado: cool 09:21:14 at least neutron/manila/ironic 09:21:42 ok let's figure out how we can do cross projects sessions efficiently 09:21:45 neutron is here :) 09:21:53 great :) 09:22:02 #action gmann to find out how we can do cross projects sessions efficiently 09:22:09 Alex_Staf: cool, 09:22:23 Alex_Staf: so will you be there on first 2 days at PTG? 09:22:35 gmann, mmmm nope 09:22:43 gmann: I'll bring ihar 09:22:46 I am not arriving unfortunately 09:22:52 even if I'll have to get him a beer 09:22:54 ohk 09:22:54 xD 09:23:02 dmellado: +1 09:23:03 +1 09:23:13 Alex_Staf: sorry for not getting you another one too, I owe you one! :D 09:23:32 +1, we need lots of beer if more cross project will join xD 09:23:37 dmellado, yes u do :) 09:23:42 how about sending mail for what all projects representative we need for what all kind of sessions ? 09:23:47 +1 09:23:48 *project represntative 09:23:56 that'd be nice 09:24:00 so that projects gets notify and they can attend/plan on interested one 09:24:10 cool 09:24:11 * Alex_Staf opens txt, "dmellado : 1 beer " :wq 09:24:12 action for oomichi to send email about the session? 09:24:20 Alex_Staf: heh 09:24:31 ok 09:24:47 great ll do that 09:25:00 anything on PTG, any query, doubt, feedback etc 09:25:34 maybe we'll have to organize some lunch/dinner there 09:25:37 do we have anyone local? 09:25:49 mtreinish ? 09:25:55 +1 we can have dinner planned 09:26:11 yea mtreinish is local only :) 09:26:40 ok let's move then 09:26:44 #topic Specs Reviews 09:26:55 #link https://review.openstack.org/#/q/status:open+project:openstack/qa-specs,n,z 09:27:17 i think most of the spec in same shape 09:27:44 anyone knows anything on HA testing one -https://review.openstack.org/#/c/399618/ 09:27:58 * dmellado checking 09:28:22 Looks stalled 09:28:27 hrm, yeah 09:28:46 we need to catch Timur on that 09:28:55 anything else on spec ? 09:29:00 +1 09:29:05 yeah, do you know if he'll be attending the PTG? 09:29:19 do not know 09:29:26 ll reach to him today 09:29:37 gmann: cool 09:29:39 cool 09:29:57 #topic Tempest 09:30:02 hi :) I dont know if this is the time to ask but I would like to know if this patch is valid and acceptable https://review.openstack.org/#/c/425211/ 09:30:06 Guys I need to consult with you regarding some cleanup decision. As in neutron/tests/tempest/scenario/ we are using functions from neutron/tests/tempest/scenario/base.py with are classmethod, we can't use in those functions addCleanup method as it requires object and not class, so where do propose to add the call for the addCleanup. 09:30:26 ekuris_: sure, we can check after meeting 09:30:33 what in your opinion is the best way to do it 09:30:36 gmann, thanks :) 09:31:00 ekuris_: I'd try for it to first pass the gates ;) 09:31:20 Alex_Staf: you can do cleanup in resource_cleanup (or tearDown if you have) 09:31:23 dmellado , ekuris_ : heh, yup 09:31:43 Alex_Staf: but any link will be more helpful to suggest the best way 09:31:53 dmellado, i know I just send it to recheck , it fails on something that not related to my patch 09:32:22 ekuris_: I have added one more recheck then we can have a look on gates if it fails 09:32:35 Alex_Staf: mainly resources created in base class function can be cleanup in teardownClass 09:32:46 gmann, https://github.com/openstack/neutron/blob/master/neutron/tests/tempest/scenario/test_basic.py 09:33:13 chandankumar, ok no problem thanks 09:33:28 Alex_Staf: and you want to clean resource created in this - setup_network_and_server 09:33:57 Alex_Staf: you should be able to do in https://github.com/openstack/neutron/blob/master/neutron/tests/tempest/scenario/base.py#L40 09:34:17 Alex_Staf: ping me or anyone if us on qa channel we can help more if needed 09:34:23 gmann, yes . In this case it is deleted due to end of class. If i wil put there another test function it will create objects for both and delete all only on the end . I do not want that 09:34:39 Sometimes if we want to"addCleanup" in resource_setup, we will use: 09:34:41 @classmethod 09:34:41 def _addCleanupClass(cls, function, *arguments, **keywordArguments): 09:34:41 cls._cleanup_resources.append((function, arguments, keywordArguments)) 09:34:57 Alex_Staf: you can then create in setUp and cleanin teardown 09:35:13 in the test ? gmann 09:35:27 if you are crating class level resource means you want those till at end 09:35:29 Alex_Staf: yes 09:35:53 Alex_Staf: setUp and terdown gets called before and after each tests respectively 09:35:58 either that or you can add a self.addCleanUp and pass the objects 09:36:11 yea 09:36:14 I think this is a good topic for the qa channel or in the free discussion? 09:36:21 let's discuss on qa channel 09:36:24 masayukig: yea 09:36:25 #link https://review.openstack.org/#/q/project:openstack/tempest+status:open 09:36:26 +1 09:36:37 so those are open review on tempest 09:37:11 ok thanks guys I need to proccess and look into all that info u provided :) 09:37:38 Alex_Staf: cool, feel free to ping if anything else needed 09:37:46 so on tempest side anything people want to discuss ? 09:37:57 i think we just keep reviewing the current patches 09:38:13 gmann, tnx man 09:38:16 Alex_Staf: also do check http://docs.openstack.org/developer/tempest/HACKING.html#test-fixtures-and-resources 09:38:36 next is Bug Triage 09:38:39 Alex_Staf: np! 09:38:47 #link https://etherpad.openstack.org/p/ocata-qa-bug-triage 09:38:52 chandankumar: seems like your turn? 09:39:14 #link report- https://etherpad.openstack.org/p/tempest-weekly-bug-report 09:39:19 dmellado, tnx I will 09:39:25 gmann: I have added the report here https://etherpad.openstack.org/p/tempest-weekly-bug-report 09:39:27 chandankumar: go ahead on this week report 09:39:39 from last two week 09:39:53 Week progress: 09:39:55 # New bugs: 0 -> 1 09:39:58 # Open bugs: 130 -> 131 09:39:59 # In-progress bugs: 59 -> 58 09:40:00 bug 130 in Launchpad itself "Multiple paragraphs in DOAP project description field" [Medium,Fix released] https://launchpad.net/bugs/130 - Assigned to Morgan Collett (morgan) 09:40:16 chandankumar: cool 09:40:31 chandankumar: anything you want to discuss on specific bug 09:40:38 I need to improve more on bug triaging, will get better incoming days 09:40:54 onme query what if a bug got a review but review got abandoned 09:41:07 chandankumar: no prob, take the open one we have to cleanup those 09:41:16 will i chnage the status of bug from inprogress to confirm 09:41:24 or will i keep as it is/ 09:41:41 chandankumar: open that again, i mean change to confirmed/triage/new state as applicable 09:42:04 got that! 09:42:05 chandankumar: yea if patches are abandon then its not in progress 09:42:25 chandankumar: thanks for your help. 09:42:35 so, one thing, https://bugs.launchpad.net/tempest/+bug/1610994 09:42:35 Launchpad bug 1610994 in tempest "test_connectivity_between_vms_on_different_networks doesn't work on OVH" [Medium,Fix released] 09:42:48 Is this really fixed? 09:43:06 I guess this is just a workaround (skip). 09:43:27 masayukig: nice catch 09:43:34 yea we should not mark it fix released 09:43:48 just keep it confirmed 09:44:21 gmann: sure, i need to improve on that 09:44:27 masayukig: Thanks for the catch 09:44:29 masayukig: can you move that back? 09:44:32 also did you guys check this email thread? 09:44:38 chandankumar: no prob we all learn like that only 09:44:42 still no open bug but interesting at least 09:44:45 http://lists.openstack.org/pipermail/openstack/2017-January/018413.html 09:45:00 gmann : yup, done 09:45:02 chandankumar : np :) 09:45:32 dmellado: not yet, ll look into that 09:45:44 dmellado: is it same thing of v3 policy one ? 09:45:56 #link http://lists.openstack.org/pipermail/openstack/2017-January/018413.html 09:46:05 gmann: yeah, it also seems that the keystone v3 non-voting gate is using the older policy.json which is compatible with v2 as well 09:46:24 which I thought it wouldn't be using 09:46:46 jamespage: thanks for bringing that out ^^ 09:47:01 looks like we have another mail also related on that 09:47:02 o/ 09:47:09 dmellado, yw 09:47:10 jamespage: hi 09:47:30 tbh it was gnuoy who tripped over the issue 09:47:57 and keystone team working on that separately right ? 09:48:25 seems like it, I'll ping rodrigods later, he ought to be sleeping now 09:49:03 but imho this is worth opening a bug 09:49:09 dmellado: rodrigods replied on mail in details 09:49:18 dmellado: but is it tempest bug ? 09:49:21 saw it, that's why I'll ask him later 09:49:34 gmann: maybe a keystone one, and point out that it affects tempest? 09:50:06 dmellado: yea and rodrigods mentioned to work in policy meeting seems 09:50:21 * masayukig needs to go in 5 min... :( 09:50:24 gmann: I'll get to talk to him later re: the bug 09:50:27 let's move on 09:50:30 let's move 10 min keft 09:51:01 let's skip DevStack + Grenade if nothing on those 09:51:08 +1 09:51:12 +1 09:51:15 #topic openstack-health 09:51:19 masayukig: ^^ 09:51:24 ok, 09:51:29 I found that, now, it seems like openstack-health gate something wrong, maybe, due to JS libraries or something. I'll try to fix it next week.. 09:51:49 #link https://review.openstack.org/#/q/project:openstack/openstack-health status:open 09:52:20 masayukig: oh 09:52:22 That's all from my side, actually 09:52:36 masayukig: thanks 09:52:43 #topic Patrole 09:52:53 #link https://review.openstack.org/#/q/project:openstack/patrole 09:52:54 is DavidPurcell around? 09:53:04 so this is RBAC testing one 09:53:18 seems like no 09:53:25 for reference on keystone v3/tempest issues (https://launchpad.net/bugs/1659515) 09:53:25 Launchpad bug 1659515 in tempest "Some tests fail when running keystone v3 with policy.v3cloudsample.json" [Undecided,New] 09:53:35 jamespage: ack, thanks! 09:54:00 sems like nice progress in patrole 09:54:18 gmann: yeah, IIRC David mentioned that they're migrating the code from the former repo 09:54:24 so progress ought to be good ;) 09:54:26 great :) 09:54:36 cool, thats very nice 09:54:45 #topic Critical Reviews 09:54:53 any critical reviews from anyone 09:55:06 ekuris_: would you like to put again your review link? ;) 09:55:26 #link https://review.openstack.org/#/c/425211/ 09:55:31 dmellado: ekuris_ this one 09:55:40 ll check this, but may be tomorrow 09:55:49 +1, I'll check once jenkins has passed 09:56:03 i have one for improving the common volume backed things in create server 09:56:06 so, I need to go, bye all, see you around :) 09:56:10 dmellado, gmann yes this one 09:56:11 #link https://review.openstack.org/#/c/405089/ 09:56:13 masayukig: get some rest! 09:56:21 ll be nice if you guys can review 09:56:23 dmellado: thanks :) 09:56:30 masayukig: thanks , bye 09:56:42 * masayukig is waving 09:56:52 if no more review then let's jump to open 09:56:57 dmellado, I add you as reviewer 09:57:03 ekuris_: ack 09:57:09 #topic Open Discussion 09:57:29 one thing i want to check who all can attend PTG 09:57:40 dmellado: zhufl ? you are in right 09:58:00 chandankumar: get budget from your boss, it will be nice to be there 09:58:02 gmann: yeah, I'll try bringin chandankumar along 09:58:05 still in discussions 09:58:12 dmellado: wow, great 09:58:39 i would like to get review to the following commit in devstack https://review.openstack.org/#/q/owner:noama%2540mellanox.com+status:open+project:openstack-dev/devstack basicly expanding stack deploy scenarios 09:58:53 zhufl: you know all details about PTG right 09:59:33 Noam_: sure, ll try to check 09:59:37 2 min left 09:59:42 anything else from anyone 09:59:48 thanks 10:00:47 let's close this 10:01:05 yea. thanks everyone for joining. 10:01:08 #endmeeting