22:01:41 <mtreinish> #startmeeting qa
22:01:43 <openstack> Meeting started Thu May 14 22:01:41 2015 UTC and is due to finish in 60 minutes.  The chair is mtreinish. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:01:44 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:01:46 <openstack> The meeting name has been set to 'qa'
22:01:54 <mtreinish> hi, who's here for today's meeting?
22:01:59 <masayukig> o/
22:02:05 <dkranz_> here, barely
22:02:28 <mtreinish> #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_May_14th_2015_.282200_UTC.29
22:02:35 <mtreinish> dkranz_: no worries, it should be quick
22:02:52 <mtreinish> being the week before summit and all
22:03:45 <mtreinish> dtroyer, jogo, hogepodge: around?
22:04:03 <hogepodge> I'm around
22:04:10 <hogepodge> o/
22:04:28 <mtreinish> ok, well let's get started maybe more people will pop up as we get started
22:04:42 <mtreinish> #topic Summit Session Etherpads
22:04:52 <mtreinish> so I started all of the etherpads for all the qa track sessions
22:05:08 <mtreinish> the links can be found here:
22:05:22 <mtreinish> #link https://wiki.openstack.org/wiki/Design_Summit/Liberty/Etherpads#QA
22:05:34 <mtreinish> I also put them all in the schedule
22:05:49 <dkranz_> mtreinish: thanks!
22:06:15 <mtreinish> if your leading the discussion in a session it'd be awesome if you could start to flush them out
22:06:25 <mtreinish> so we've got a good starting ground going into the sessions
22:06:41 <jogo> mtreinish: a little bit
22:07:28 <mtreinish> that's all I had for this topic, is there anything else?
22:08:48 <mtreinish> ok, then let's move on
22:08:59 <mtreinish> #topic Grenade
22:09:09 <mtreinish> jogo: anything on the grenade front this week?
22:10:16 <jogo> sdague is working on some patches that don't work yet
22:10:29 <jogo> we did hit a bug related to upgrading OSC in grenade/devstack
22:10:47 <mtreinish> oh, the cinderclient thing?
22:12:50 <mtreinish> heh, I guess so :)
22:12:55 <mtreinish> ok is there anything else on grenade?
22:14:07 <mtreinish> ok, then let's move on
22:14:22 <mtreinish> #topic Devstack
22:14:36 <mtreinish> I don't think dtroyer is around right now
22:14:46 <mtreinish> and I don't have anything to add for devstack this week
22:14:55 <mtreinish> does anyone else have something to discuss about devstack?
22:16:21 <mtreinish> ok, then let's move on
22:16:29 <mtreinish> #topic Bugs
22:16:58 <mtreinish> so does anyone have anything to bring up about open bugs?
22:17:06 <mtreinish> or the status of the bug list
22:17:31 * mtreinish has a feeling it's going to be 1-2-3 for each topic today :)
22:17:34 <hogepodge> I have a topic relating to defcore and how we interact with bugs, but it's a larger issue and not directed at any bug in particular.
22:17:46 <mtreinish> hogepodge: sure, as good a time as any
22:18:21 <hogepodge> I drafted a proposal to put before the board, regarding flagging of tests, that would require vendors to document bugs and encourage them to with fix, or have a plan to fix.
22:18:32 <hogepodge> You can see it here: https://review.openstack.org/#/c/182105/
22:18:43 <mtreinish> #link https://review.openstack.org/#/c/182105/
22:18:48 <hogepodge> Feedback is encouraged, since this will have an impact on the qa team.
22:19:03 <masayukig> mtreinish: We have 17 new bugs..
22:19:38 <masayukig> mtreinish: We should triage them.
22:19:38 <mtreinish> masayukig: heh, I have a feeling hogepodge knows something about that. I think a lot are from people running defcore :)
22:19:54 <mtreinish> masayukig: yeah I've been a bit lax the past couple weeks
22:20:13 <mtreinish> masayukig: did someone sign up to triage this week?
22:20:30 <masayukig> mtreinish: afazekas?
22:20:39 <hogepodge> mtreinish: masayukig see link above. :-)
22:21:02 <mtreinish> hogepodge: sure, that seems like a sane approach. Personally I have no qualms about closing tempest bugs which are just noise
22:21:40 <mtreinish> hogepodge: I think part of the proposal should probably point out that the tests may (or more probably) aren't the source of the bugs
22:22:03 <mtreinish> because like if a feature doesn't work in a service with a certain config and tempest is exposing that, that's not a tempest bug
22:22:12 <hogepodge> mtreinish: I can update the wording. It'a part of why I indicated that either the test or upstream could be patched.
22:22:12 <mtreinish> which the common issue I see
22:22:20 <hogepodge> mtreinish: agree
22:22:25 <mtreinish> hogepodge: sure, I'll leave a review comment about that
22:23:20 <mtreinish> masayukig: yeah it looks like afazekas signed up for the rotation this week:
22:23:23 <mtreinish> #link https://etherpad.openstack.org/p/qa-bug-triage-rotation
22:23:31 <hogepodge> If it's a cloud config problem, then there should be no flag. Once a test is flag the flag can't be removed for that cycle, so I'm trying to introduce a barrier to make sure we're not excluding tests for bad reasons
22:24:01 <mtreinish> hogepodge: oh, I didn't realize the turnaround was that long on flags
22:24:12 <mtreinish> yeah there should be a high barrier to doing it then
22:24:53 <dkranz_> mtreinish: we need to determine if the bug is in the cloud-under-test or a but in tempest that is exposed by a new config that we don't test
22:25:21 <mtreinish> dkranz_: sure, there are legit bugs being filed about that
22:25:30 <dkranz_> mtreinish: I can look at some of these tomorrow
22:25:32 <mtreinish> but at least this past week or 2 most are not about that
22:26:11 <mtreinish> when tempest bugs in other configs have come up I've been pretty quick to try and fix it
22:26:48 <mtreinish> ok, is there anything else on bugs?
22:27:54 <mtreinish> ok, then let's move on
22:27:59 <mtreinish> #topic Critical Reviews
22:28:15 <mtreinish> does anyone have any reviews they'd like to get extra eyes on?
22:28:57 <mtreinish> I've got a couple this week:
22:28:59 <mtreinish> #link https://review.openstack.org/182684
22:29:06 <mtreinish> #link https://review.openstack.org/183035
22:29:14 <mtreinish> #link https://review.openstack.org/182139
22:29:30 <mtreinish> #link https://review.openstack.org/178341
22:29:46 <mtreinish> I think that's it for me :)
22:29:51 <dkranz_> https://review.openstack.org/#/c/179398/
22:30:08 <dkranz_> That's the last for making non-admin work
22:30:19 <masayukig> #link https://review.openstack.org/#/c/179398/
22:30:22 <mtreinish> dkranz_: oh, sry I have that open in a tab somewhere, I guess I never finished
22:30:49 <dkranz_> mtreinish: I"ll look at the ones you listed first thing tomorrow
22:31:19 <mtreinish> dkranz_: cool, thanks
22:31:39 <mtreinish> most of them should be pretty quick
22:31:48 <hogepodge> Oh, this https://review.openstack.org/#/c/182730/
22:32:05 <hogepodge> #link https://review.openstack.org/#/c/182730/
22:33:11 <mtreinish> oh an ordering issue, jlk fixed one of those for the resize tests in the same class
22:33:19 <mtreinish> that server reuse is jsut a pain
22:33:46 <mtreinish> ok are there any other reviews?
22:35:19 <mtreinish> ok, then let's open the floor
22:35:23 <mtreinish> #topic Open Discussion
22:35:34 <mtreinish> does anyone have any topics not on the agenda to bring up?
22:36:10 <mtreinish> oh, I have a couple info worthy items actually
22:36:20 <mtreinish> #info tempest now gating on py34 unit tests
22:36:43 <mtreinish> that landed earlier this week, we now have a py34 unit test job gating on all tempest changes
22:36:43 <masayukig> mtreinish: cool :)
22:36:49 <dkranz_> woot
22:37:00 <mtreinish> tempest itself doesn't quite work yet under python34
22:37:04 <mtreinish> but the unit tests are a start
22:37:44 <mtreinish> #info kilo jobs added to tempest check
22:37:59 <mtreinish> that landed about the same time, and was mostly an oversight from the release
22:38:10 <mtreinish> but I added all the missing stable compat kilo jobs to the tempest queue
22:38:25 <mtreinish> so now each tempest change requires a bunch more things to pass :(
22:38:34 * mtreinish can't wait until icehouse dies
22:39:03 <mtreinish> ok is there anything else?
22:39:30 <mtreinish> otherwise we can call the meeting
22:39:33 <dkranz_> mtreinish: why can't we kill icehouse?
22:40:01 <dkranz_> mtreinish: you can answer that next week :)
22:40:05 <mtreinish> dkranz_: because the proposed deadline for doing that is still a few months off (July iirc)
22:40:29 <dkranz_> mtreinish: ok :(
22:40:43 <mtreinish> it was an experiment in having a longer window, which I personally view as a failure
22:41:42 <mtreinish> anyway I guess that's it for today
22:41:45 <mtreinish> thanks everyone
22:41:53 <mtreinish> looking forward to meeting f2f in vancover
22:42:16 <mtreinish> #info no irc meeting next week because of summit
22:42:26 <mtreinish> #endmeeting