17:01:23 <dkranz> #startmeeting qa
17:01:24 <openstack> Meeting started Thu Nov 21 17:01:23 2013 UTC and is due to finish in 60 minutes.  The chair is dkranz. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:25 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:01:28 <openstack> The meeting name has been set to 'qa'
17:01:38 <dkranz> Agenda: https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
17:01:46 <dkranz> So who is here today?
17:01:55 <afazekas> hi
17:01:58 <mlavalle> dkranz: hi
17:02:19 <tkammer> hey
17:02:25 <andreaf> hi
17:02:26 <qianlin> hi
17:02:55 <dkranz> mkoderer: Here?
17:05:17 <dkranz> Sory, I was in the wrong channel
17:05:29 <dkranz> A master blueprint was created for icehouse scenario tests and it has several pointers in it.
17:05:47 <dkranz> Several people are adopting the approach of creating a spec in a zeroth patch.
17:06:26 <dkranz> Any comments about blueprints
17:06:32 <dkranz> ?
17:07:03 <afazekas> link ?
17:07:05 <andreaf> I created a blueprint for input scenarios for scenario tests
17:07:07 <mlavalle> dkranz: I have 2 blueprints for icehouse… I want to make sure they are aligned with the new effort to improve Neutron testing
17:07:14 <andreaf> as discussed during summit
17:08:14 <andreaf> sorry mlavalle go ahead first
17:08:38 <dkranz> mlavalle: Are they created yet in tempest?
17:08:52 <mlavalle> mlavalle: dkranz: those blueprints were put together several months ago… so I want to confirm they are aligned with the new priorities
17:09:13 <dkranz> mlavalle: links?
17:09:17 <mlavalle> dkranz: t=yes they are in Launchpad
17:10:02 <dkranz> mlavalle: Do you mean this https://blueprints.launchpad.net/tempest/+spec/neutron-advanced-scenarios
17:10:29 <mlavalle> dkranz: nope, hold on a second… I have trouble with my Launchpad account
17:11:14 <dkranz> mlavalle: We are tracking the new scenarios in https://blueprints.launchpad.net/tempest/+spec/add-scenario-tests-in-icehouse
17:11:24 <dkranz> mlavalle: which includes both neutron and other
17:12:00 <dkranz> mlavalle: Any good neutron scenario tests will be helpful and this blueprint should help avoid duplication.
17:12:00 <salv-orlando> Do we still need the first? I filed it before the summit, but I think it will all go under the latter
17:12:03 <mlavalle> dkranz: so what is here is not valid anymore: https://blueprints.launchpad.net/tempest
17:12:23 <dkranz> mlavalle: Not sure what you mean.
17:12:57 <dkranz> salv-orlando: Yes, it would be reasonable to break your blueprint into its pieces and point to from the master blueprint
17:13:22 <salv-orlando> dkranz: ok will do
17:13:40 <mlavalle> dkranz: well, I thought that's where blueprints were registered and prioritized… if that's not the place anymore, it's fine, I just need to know it
17:13:51 <dkranz> salv-orlando: Thanks
17:14:19 <dkranz> mlavalle: THe high priority is "more scenario tests" and is tracked through the master blueprint
17:14:35 <dkranz> mlavalle: We did not want to manage a whole lot of blueprints
17:14:38 <mlavalle> dkranz: cool, thanks
17:14:54 <dkranz> mlavalle: The new scenarios are more on a "train model" where they come in when they do
17:15:11 <dkranz> mlavalle: We are not assigning individual priorities and tracking them
17:15:35 <dkranz> Anything else on that?
17:15:38 <andreaf> dkranz: I have a blueprint which is a tool around scenarios,  to provide multiple input scenarios: https://blueprints.launchpad.net/tempest/+spec/input-scenarios-for-scenario
17:15:59 <andreaf> dkranz: I think that's a bit different, I wouldn't add it into the list
17:16:32 <dkranz> andreaf: I agree. Looks interesting.
17:16:51 <dkranz> #topic Negative testing
17:17:15 <dkranz> So Marc and I have not had time to make much progress on this since last week.
17:17:24 <dkranz> We hope to do some more next week.
17:17:49 <dkranz> BTW, next week is US Thanksgiving holiday so many of us will not be around.
17:18:24 <dkranz> #topic Neutron testing
17:18:28 <dkranz> mlavalle: all yours
17:18:50 <mlavalle> dkranz: well, this topic is related to my previous question
17:19:25 <mlavalle> dkranz: sdague wrote in an emasil a few days ago that certain things needed to be finished ready for the Montreal sprint
17:20:03 <dkranz> mlavalle: Yes, I think he was trying to make sure that the Montreal thing was a "wrap-up" session and not a "let's start now" thing
17:20:18 <mlavalle> dkranz: i am attending the Montreal sprint and want to know how can i contribute between now and January for it to be a success
17:21:09 <dkranz> mlavalle: You can look at https://etherpad.openstack.org/p/icehouse-summit-qa-neutron
17:21:29 <mlavalle> dkarnz: ok, I'll take a look, thanks
17:21:38 <dkranz> mlavalle: There is also a need for new scenario tests.
17:21:47 <sdague> hey folks, actually managed to make it late... :) (dkranz carry on, don't let me interupt your flow)
17:22:14 <dkranz> mlavalle: You should probably coordinate with the neutron folks mentioned there
17:22:18 <mlavalle> dkranz: who should I talk to to coordinate scenario tests development?
17:22:19 <salv-orlando> mlavalle: markmcclain and anteaya are coordinating efforts
17:22:23 <dkranz> sdague: Welcome
17:22:41 <salv-orlando> I am participating but I am merely an executor
17:22:54 <mlavalle> salv-orlando: ok, I will talk to anteaya
17:22:59 <dkranz> mlavalle: The master blueprint is the registry to avoid duplication
17:23:23 <dkranz> mlavalle: Anything else?
17:23:41 <mlavalle> dkranz: that's all, thanks for all the answers
17:24:02 <dkranz> #topic Critical reviews
17:24:32 <dkranz> It would be great if some one could give a +A (or not) to https://review.openstack.org/#/c/55251/
17:24:47 <dkranz> It is awaiting non-RH approval
17:25:01 <dkranz> Any other reviews folks want to call out?
17:25:25 <dkranz> sdague: What is the gate status? Business as usual or "no +2"?
17:25:51 <sdague> dkranz: the grenade fix just landed
17:26:07 <dkranz> sdague: Cool
17:26:12 <sdague> so... I think it's going to take a couple of hours to figure out if that makes most of the issues go away
17:26:25 <dkranz> sdague: OK, so we'll hold off for now.
17:26:35 <sdague> I'd say hold off on tempest +A until we know
17:26:46 <sdague> as there are already 50 things in the gate, and don't want to make it worse
17:26:49 <dkranz> sdague: I presume there will be another email from infra when things are "ok"
17:26:54 <sdague> yeh
17:27:20 <dkranz> sdague: I think we may need to modify our gating strategy but that is not a topic for now.
17:27:27 <sdague> agreed
17:27:49 <afazekas> #link https://review.openstack.org/#/c/57193/
17:27:49 <dkranz> ok, then
17:27:55 <dkranz> #topic General Discussion
17:27:57 <afazekas> is this change still needed ?
17:28:11 <sdague> dkranz: agreed, I'm having dinner with jeblair and jog0 tonight, I'm sure it will come up
17:29:14 <dkranz> afazekas: Not sure
17:29:52 <dkranz> sdague: Can you comment on ^^^. You pushed it through (or tried to)
17:30:54 <sdague> last night we were trying to sort out anything else that might help us on stability
17:31:09 <sdague> clarkb and jog0 felt that was one of the things that would help
17:31:32 <dkranz> afazekas: You gave it a -1
17:31:33 <clarkb> afazekas: yes it is needed
17:31:50 <clarkb> 1251920 is currently the biggest gate problem and 57193 works around it for now
17:32:25 <dkranz> So it just needs a reverify
17:32:33 <clarkb> dkranz: it is in the gate now
17:32:44 <dkranz> clarkb: ok
17:32:55 <afazekas> dkranz: yes because the big in the skip decorator is in Fix committed status
17:33:19 <clarkb> 1251920 is definitely not fixed I think that should be changed
17:33:39 <afazekas> several other bug was also marked as duplicate of that bug
17:33:56 <clarkb> oh the oslo sync change marked it fixed but it didn't actually fix the bug
17:34:16 <clarkb> afazekas: I think that bug should be marked invalid for nova and triaged for tempest
17:34:36 <sdague> clarkb: so I ran recheck to get new results, did you reverify to put it back in the gate?
17:34:45 <afazekas> https://bugs.launchpad.net/neutron/+bug/1251784 and this ?
17:34:46 <clarkb> sdague: something else got it in the gate
17:34:49 <uvirtbot> Launchpad bug 1251784 in tripleo "nova+neutron scheduling error: Connection to neutron failed: Maximum attempts reached (dup-of: 1251920)" [Critical,New]
17:34:50 <uvirtbot> Launchpad bug 1251920 in nova "Tempest failures due to failure to return console logs from an instance" [Critical,Fix committed]
17:34:52 <clarkb> sdague: I am not sure what :) but it is there
17:35:07 <sdague> heh
17:36:01 <clarkb> afazekas: I think the confusion here is we thought the nova oslo sync would fix several problems
17:36:04 <dkranz> This is kind of a mess
17:36:14 <clarkb> afazekas: it did fix 1251784 but no 1251920
17:36:18 <clarkb> so they need to be deduped
17:37:14 <clarkb> yes it is a mess
17:37:24 <sdague> dkranz: it is kind of a mess, thankfully clarkb and jog0 have been unwinding it
17:37:36 <clarkb> I am going to start drafting up a thing in the etherpad that has been tracking it sothat we can make sense of it all
17:37:44 <dkranz> clarkb: Thanks.
17:37:58 <dkranz> clarkb: Then we can adjust the state of bugs, etc.
17:38:04 * sdague owes clarkb plenty of beer
17:38:26 <dkranz> Any other issues to discuss?
17:39:02 <afazekas> instance validation via ssh ?
17:39:03 <dkranz> OK, I guess we can end early today.
17:39:16 <dkranz> afazekas: Can you elaborate?
17:39:33 <afazekas> https://review.openstack.org/#/c/52870/
17:39:59 <dkranz> afazekas: Looks like it is just waiting for +A
17:40:00 <afazekas> https://review.openstack.org/#/c/52586/
17:40:10 <sdague> afazekas: I'll look
17:40:29 <afazekas> sdague: thx
17:40:33 <dkranz> afazekas: The last is not ready for review
17:40:39 <sdague> so the last jenkins success was a month ago, I'm going to recheck it
17:40:42 <afazekas> it is
17:40:44 <sdague> and if it looks good, will +A
17:41:04 <dkranz> afazekas: It says work in progress and depends on an abandoned patch?
17:41:14 <afazekas> I have changed the default behavior to connect via the fixed ip based on sdagues request
17:41:35 <afazekas> if I would change the default to floating , it would pass on the gate
17:42:41 <afazekas> https://review.openstack.org/#/c/50337/
17:42:43 <afazekas> sorry
17:42:45 <afazekas> restored
17:43:34 <dkranz> afazekas: ok, I'll look too
17:43:59 <dkranz> Anything else?
17:44:36 <dkranz> Should we cancel next week or does some one non-US want to lead?
17:45:10 <anteaya> o/
17:45:28 <dkranz> anteaya: Yes?
17:46:46 <dkranz> ok, I guess that's it for today.
17:46:59 <sdague> afazekas: did you vote for core adds on the public list?
17:47:16 <sdague> I think you were the last tempest-core unaccounted for?
17:47:38 <anteaya> just responding to my name earlier
17:47:42 <anteaya> sorry
17:48:18 <afazekas> sdague: I will, thank you
17:48:45 <anteaya> oh I do have a comment
17:48:59 <anteaya> I can't make the neutron team meeting next week
17:49:18 <anteaya> would be great if someone could take my spot for Neutron Tempest topic
17:49:29 <anteaya> I will try to populate the agenda item on Sunday
17:49:32 <anteaya> any takers?
17:49:36 <dkranz> anteaya: When is it?
17:49:46 <anteaya> Monday at 21 utc I think
17:50:32 <mlavalle> anteaya: I can do it
17:50:40 <anteaya> Weekly on Mondays at 2100 UTC
17:50:53 <anteaya> awesome thanks mlavalle I'll co-ordinate with you
17:51:00 <anteaya> that's it from me
17:51:17 <dkranz> ok
17:51:22 <dkranz> #endmeeting