17:00:06 <sdague> #startmeeting qa
17:00:07 <openstack> Meeting started Thu Sep 26 17:00:06 2013 UTC and is due to finish in 60 minutes.  The chair is sdague. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:08 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:10 <openstack> The meeting name has been set to 'qa'
17:00:19 <sdague> hey, who's around for the QA meeting?
17:00:22 <dkranz> Hi
17:00:24 <mtreinish> o/
17:00:48 <sdague> #link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
17:00:54 <sdague> agenda listed in the link
17:01:13 <sdague> #topic Blueprints (sdague)
17:01:32 <kwhitney> Hi
17:01:44 <sdague> I need to do some blueprint clean up tonight, I'll do that once I ride my bike home. Try to get things to reflect reality
17:02:01 <sdague> anyone want to provide updates for open blueprints (beyond the 2 special ones listed in the agenda)
17:02:06 <mkoderer> Hi sorry I am late
17:02:27 <sdague> no worries
17:02:33 <mtreinish> sdague: how many targeted open blueprints do we have for H
17:02:49 <sdague> mtreinish: too many
17:03:08 <dkranz> sdague: I should check the status of client-lib stability
17:03:20 <dkranz> sdague: It is a tempest blueprint but the work is being done by mordred
17:03:35 <sdague> yeh, that actually caused a really interesting issue with the cliff gate break
17:03:40 <sdague> because of neutron client renaming
17:03:42 <dkranz> sdague: It was waiting for reviews last I looked
17:04:00 <sdague> so we're actually testing old servers with new clients
17:04:05 <sdague> on stable branches
17:04:20 <dkranz> sdague: I guess the code merged then :)
17:04:20 <mordred> I didn't do it
17:04:31 <mordred> oh - wait - yeah, I'm working on that and am almost there
17:04:31 <mtreinish> sdague: https://blueprints.launchpad.net/tempest/havana it doesn't look like that many (that are not implemented)
17:04:34 <sdague> mordred: well, I think at some point the defaults changed
17:04:48 <dkranz> mordred: Yes, that was what I was referencing
17:05:09 <mordred> https://review.openstack.org/#/c/41945/ and https://review.openstack.org/#/c/41931/
17:05:10 <sdague> mtreinish: ok, well I'd try to get us cleaned up anyway
17:05:13 <mordred> for anyone following along at home
17:05:36 <dkranz> mordred: Yes. What is needed to push that through?
17:05:37 <sdague> and adding targets for icehouse, so we can start thinking about that
17:05:52 <mordred> dkranz: I just need to get infra folks to re-review the first one
17:06:04 <dkranz> mordred: OK, cool
17:06:07 <sdague> mordred: great
17:06:50 <sdague> ok, next up
17:06:54 <sdague> #topic Bogus errors in logs (dkranz)
17:07:08 <dkranz> sdague: So I am going to create a blueprint for this
17:07:17 <sdague> and mlavalle let me know if you are here for the next topic
17:07:22 <sdague> dkranz: great
17:07:25 <dkranz> I filed some bugs with a few more to go tagged as error-in-logs
17:07:26 <mlavalle> sdague: I am
17:07:57 <dkranz> sdague: I think we should put the whitelist check in tempest code repo so we can update it easily
17:08:05 <sdague> dkranz: agreed
17:08:11 <dkranz> sdague: As part of the tox job
17:08:21 <sdague> I was actually going to start in on stubbing that after the meeting
17:08:31 <dkranz> sdague: I'm a little worried about flaky log fails once we do this
17:08:47 <dkranz> The current flakiness is bad already
17:08:50 <sdague> well, we can run in a non blocking way to begin with
17:09:05 <sdague> and figure out how bad it would be, logstash actually makes that easy
17:09:10 <dkranz> sdague: Yeah, that's a good idea
17:09:20 * sdague <3 logstash
17:09:44 <sdague> I actually need to con clarkb into adding it to devstack :)
17:10:06 <dkranz> sdague: I'm not sure how we can report the log failures but not fail the build in a good way
17:10:09 <sdague> dkranz: ok, let me know as soon as you get the blueprint filed and stubbed
17:10:11 <dkranz> sdague: Can we post a review comment
17:10:19 <dkranz> sdague: Will do
17:10:29 <sdague> dkranz: so to begin with we can just print out content as part of the tempest run
17:10:38 <sdague> then use logstash to figure out how often we'd have broken
17:10:50 <sdague> eventually we're going to need to hard fail on this
17:10:54 <dkranz> sdague: OK.
17:10:59 <sdague> but we can figure that out later
17:10:59 <dkranz> sdague: Agreed.
17:11:10 <sdague> there is plenty of plumbing code regardless.
17:11:25 <dkranz> sdague: I'll put some work items in the blueprint
17:11:31 <sdague> sounds good
17:11:51 <dkranz> sdague: I think that's it for this topic
17:11:52 <sdague> dkranz: are you getting reasonable uptake by projects on the bugs?
17:11:59 <sdague> dkranz: great
17:12:05 <sdague> ok, next topic
17:12:13 <sdague> #topic neutron testing status (mlavalle)
17:12:17 <dkranz> sdague: The heat one was marked as icehouse with med priority
17:12:18 <mlavalle> sdague: I spent this week working with mtresinish, afazekas and dkranz (thank you all for your help) debugging the new isolated networks code added to isolated credentials
17:12:28 <sdague> mlavalle: great
17:12:41 <mlavalle> sdague: it merged this morning.
17:12:42 <mtreinish> mlavalle: it merged earlier today
17:12:58 <sdague> ok, so where does that leave us in the full runs?
17:13:01 <mlavalle> I will synch up with mtreinish to define the next step with that
17:13:19 <mtreinish> sdague: this is just to enable parallel with neutron
17:13:32 <mlavalle> I need to go back to the full runs blueprint and review the status
17:13:34 <sdague> ok, I just noticed neutron gate jobs don't have the full runs enabled
17:13:42 <sdague> shouldn't we turn those back on?
17:13:49 <sdague> I mean in the check queue
17:13:59 <mlavalle> not yet. Let me evaluate over the next couple of days
17:14:09 <mtreinish> sdague: I don't think anyone looks at them if they always fail
17:14:20 <mtreinish> now if you made them gating :)
17:14:21 <sdague> mtreinish: ok, it's just hard to figure out how bad they are failing
17:14:22 <mlavalle> and I'll get back to you. I am talking about full run
17:14:30 <sdague> given that we have no data right now
17:14:43 <mtreinish> sdague: I think they are on the experimental queue
17:14:49 <mtreinish> so you can manually trigger them
17:14:50 <sdague> ok
17:14:51 <mlavalle> sdague: I agree with you. I need some fresh runs to gauge where we stand
17:14:53 <dkranz> mtreinish: They are
17:15:01 <sdague> mlavalle: ok, great
17:15:41 <mlavalle> mtreinish: I'll look for the experimental queue and do some runs
17:15:53 <mlavalle> if I need help, i'll ping you
17:15:55 <sdague> mlavalle: it would be great to see if we could get it down to a short list of bugs that are blocking things
17:16:04 <mtreinish> mlavalle: ok
17:16:06 <mlavalle> sdague: agree
17:16:16 <mlavalle> That's my intent
17:16:31 <mlavalle> That's all I have
17:16:32 <sdague> I'm assuming we're talking icehouse-1 at this point, but still would like to keep priority on it
17:16:53 <mlavalle> sdague: most likely, but i'll let you know early next week
17:16:54 <sdague> we'll probably do a session or two at summit with the neutron team to try to come up with longer term strategies here
17:16:55 <dkranz> mlavalle: Just do 'check experimental" in a tempest patch
17:16:58 <sdague> great
17:17:13 <sdague> ok, next topic...
17:17:17 <mlavalle> dkranz: thanks
17:17:28 <sdague> #topic rework "skip test" functionality, reprises mkoderer's proposal (gfidente)
17:17:44 <mkoderer> giulivo: you around?
17:17:52 <mlavalle> mlavalle: I have to run to another meeting… see you around guys
17:18:09 <sdague> thanks mlavalle
17:18:13 <giulivo> yep so I submitted a few changes to enforce a strict checking of the skip messages and hopefully get the tracker to count them all
17:18:26 <sdague> giulivo: ok, are there reviews you need eyes on?
17:18:29 <mkoderer> #link https://review.openstack.org/#/c/48121/
17:18:38 <giulivo> nope but the suggestion which popped was to just make that a decorator
17:18:55 <giulivo> so that would change a bit how we use/count the skips, is that okay to everyone to change?
17:19:14 <sdague> yes, that's fine by me
17:19:19 <mtreinish> giulivo: its fine if it makes things simpler and consistent
17:19:44 <mkoderer> I looking forward to the patch :)
17:19:49 <giulivo> ok, that was all from me then, just looking for some sort of okay
17:20:04 <sdague> yep, +1. look forward to reviewing it :)
17:20:15 <sdague> ok, last schedule topic
17:20:23 <sdague> #topic Critical Reviews (sdague)
17:20:43 <sdague> ok, now is the time to bring up reviews that you think we've let fall through the cracks, or became contentious
17:20:52 <mtreinish> this is a devstack one: https://review.openstack.org/#/c/46314/
17:21:02 <mtreinish> to enable tenant isolation on neutron runs
17:21:21 <mtreinish> it's only been mergeable since this morning
17:21:50 <sdague> ok, +2 from me, can you hit up dtroyer after the meeting to get the other +2?
17:21:58 <sdague> other reviews
17:22:01 <mtreinish> sdague: sure
17:22:33 <sdague> mkoderer: did your stress test change merge through?
17:22:50 <mkoderer> sdague: yes
17:22:54 <sdague> ok, great
17:22:58 <mkoderer> it's was merged this morning
17:23:08 <mkoderer> so we will see the results next days
17:23:13 <sdague> ok, cool, so hopefully that fixes the cron job tonight
17:23:31 <sdague> otherwise I actually feel like we're keeping up pretty well
17:23:31 <mkoderer> sdague: yes I hope so :)
17:23:48 <sdague> great to have mkoderer and giulivo on the team with reviews
17:23:59 <sdague> ok, lets switch to ...
17:24:05 <sdague> #topic Open Conversation
17:24:36 <mtreinish> well I guess I should mention that elastic-recheck is now in gerrit
17:24:37 <sdague> I guess the only thing that I wanted to say is next week I'll set aside some time for design summit conversations about the talks we want there in the track
17:24:51 <mtreinish> https://review.openstack.org/#/q/status:open+project:openstack-infra/elastic-recheck,n,z
17:24:59 <adalbas> sdague, about the blueprints triage, i believe this one can be closed: https://blueprints.launchpad.net/tempest/+spec/upgrade-testing-in-gate
17:25:16 <giulivo> mtreinish, +1 thanks for that
17:25:18 <sdague> adalbas: great, will do
17:25:27 <dkranz> mtreinish: That's great. Hopefully fewer people will 'recheck no bug'
17:25:40 <mtreinish> dkranz: it's still running on my laptop at this point
17:25:47 <dkranz> mtreinish: :)
17:25:50 <sdague> dkranz: +1, mtreinish, jog0 and clarkb did a great job here
17:25:56 <mtreinish> hopefully we'll get it up on infra shortly
17:26:53 <mtreinish> but everyone should feel free to contribute to elastic-recheck to make it better :)
17:26:54 <sdague> it's very cool that elastic-recheck has become a thing :)
17:26:59 <sdague> definitely
17:27:42 <sdague> everyone with tempest +2 has +2 on that repo, so you can approve in new bug patterns
17:27:49 <sdague> which is probably something we should mention
17:28:08 <dkranz> Good to know
17:28:28 <sdague> ok, anything else from folks?
17:28:37 <sdague> other topics for open discussion?
17:29:50 <annegentle> sdague: hey
17:30:01 <sdague> annegentle: hey
17:30:10 <annegentle> general question -- is there interest in reviewing docs prior to the release?
17:30:28 <sdague> annegentle: can you specify what kind of docs?
17:30:42 <dianefleming> hey hey
17:30:44 <annegentle> For example, if I set up a doc review blitz for API docs and operator docs, would QA want to read-read-read?
17:31:01 <annegentle> my sense is that QAers are mostly interested in api docs
17:31:16 <sdague> we could open it up to folks for sure, I think like you said, on the API side there is probably the most interest
17:31:40 <annegentle> okay, I'll see if I can come up with a plan and date
17:31:41 <afazekas> sounds good to me
17:31:46 <annegentle> dianefleming: sound good to you?
17:31:47 <sdague> sounds good
17:32:00 <annegentle> me and dianefleming are doing an "output test blitz" tomorrow
17:32:01 <sdague> we'll encourage folks to participate
17:32:06 <sdague> cool
17:32:14 <annegentle> but then I thought QAers might like a blitz we open up to more people
17:32:17 <dianefleming> sounds good
17:32:20 <annegentle> ok, thanks sdague
17:32:23 <annegentle> that's all I had
17:32:26 <sdague> great
17:32:32 <sdague> ok, any last topics from folks?
17:32:41 <sdague> going once...
17:32:51 <sdague> going twice...
17:33:03 <sdague> ok, lets call it a meeting.
17:33:16 <sdague> thanks for coming everyone, we'll see you in #openstack-qa
17:33:20 <sdague> #endmeeting