18:02:21 #startmeeting cue 18:02:21 Meeting started Mon Jun 8 18:02:21 2015 UTC and is due to finish in 60 minutes. The chair is sputnik13. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:02:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:02:25 The meeting name has been set to 'cue' 18:02:31 role call, sound off 18:02:33 1 18:02:36 o/ 18:02:53 hello! 18:02:55 hello 18:03:51 you guys are horrible at this, sound off one two three four, etc 18:03:52 :-P 18:04:01 where's dkalleg ? 18:05:02 sputnik13: :p didn't know we were playign that game 18:05:59 dkalleg is indisposed I guess, let's start the meeting! 18:06:12 we have... dun dun duuuuunnnnn 18:06:14 agenda! 18:06:17 https://wiki.openstack.org/wiki/Meetings/Cue 18:06:40 our next meeting is no longer in the past 18:06:41 :) 18:06:50 nice 18:07:13 thx for updating that 18:07:15 #topic Open Action Items 18:07:23 http://eavesdrop.openstack.org/meetings/cue/2015/cue.2015-06-01-18.01.html 18:07:58 vipul no problem, I might get it done sooner than 12 hours before the meeting for next week ;) 18:08:13 davideagnello you first 18:08:40 ok, so Rally job is currently in review 18:08:58 https://review.openstack.org/#/c/187620/ 18:09:13 #info davideagnello to look into getting Rally gate job added 18:09:18 the CI job was created by Sergey Skripnick 18:09:27 #link https://review.openstack.org/#/c/187620/ 18:09:48 who's sergey? 18:09:55 I thought Boris was the rally guy 18:10:09 looks like it passed jenkins tests and waiting to be merged in 18:10:20 I am not sure 18:10:35 well, I'm not one to look the gift horse in the mouth 18:10:55 sorry, hi 18:11:04 haha yes 18:11:16 2 18:11:22 see, dkalleg gets is 18:11:27 s/is/it 18:11:52 fashionably late though he may be 18:12:12 ok, so we're just waiting for it to merge? 18:12:21 so at this point who would we talk to in order to get this added? 18:12:26 sputnik13: yes 18:12:31 added as in what 18:12:36 merged 18:12:41 talk to someone in #openstack-infra 18:12:48 hmm, I don't know, maybe camp out at #openstack-infra 18:12:52 yeah, what vipul said 18:12:55 ok 18:13:10 you like the great outdoors, go camping :) 18:13:26 this should be straight forward, it's an experimental check -- should be merged if we ask 18:13:28 *crickets* 18:14:22 davideagnello once that's merged do we need changes to our repo? 18:14:36 sputnik13: we shouldn't have to 18:14:40 ok 18:14:46 #action davideagnello to follow up on rally job merge 18:15:01 next topic? 18:15:34 #topic esmute to making tempest rabbit gate job voting 18:16:10 it's not voting yet, but the test looks stable 18:16:20 being that esmute is out and someone (me) neglected to follow up with him, let's get status on this next week 18:16:23 davideagnello: does it? i haven't seen it pass that often 18:16:30 davideagnello: define "stable" 18:16:31 maybe i am looking at the wrong patches 18:17:04 in the last four outstanding patches, the test are passing 18:17:26 total runtime is around 40 min 18:17:34 no no, what we're looking for are consistently passing 18:17:57 ok, over how many iterations? 18:18:05 #link https://review.openstack.org/#/c/187273/6 18:18:12 that's where we're trying to track it right? 18:18:37 of the last 4 attempts 2 failed 18:18:52 I'm not sure how that coincides with the rabbit stability patch being merged 18:19:03 o/ 18:19:06 just peeking in ) 18:19:07 but it doesn't seem stable at this point 18:19:12 ekarlso welcome 18:19:18 when was your cloud config fix merged in? 18:19:48 seems to be since the port delete and oscloud config changes where made 18:20:05 6/3 18:20:27 so the 2 failures could have been before the merge and the 2 successes were definitely after the change 18:20:55 but 1 day of tests following a fix doesn't seem to match the bar we agreed to 18:21:09 which was about 1 week of testing to ensure it's stable 18:21:20 I agree, we should give it more time, but it is looking better 18:21:37 it's definitely looking better, agree 100% there :) 18:22:06 I think we should continue to run rechecks this week and check on this again next week 18:22:47 I think that patch might need to be rebased as well 18:22:54 not positive 18:23:07 ok, will get it updated 18:23:27 #startvote postpone decision on tempest gate until 6/15 18:23:28 Unable to parse vote topic and options. 18:23:33 bleh 18:23:47 lol 18:24:08 you need to provide options :P 18:24:22 like how 18:24:35 #startvote Should we vote now? Yes, No, Maybe 18:24:36 Only the meeting chair may start a vote. 18:24:37 ah I see it 18:24:49 #link http://docs.openstack.org/infra/system-config/irc.html#voting 18:24:58 #startvote Postpone decision on tempest gate until 6/15? Yes, No 18:24:59 Begin voting on: Postpone decision on tempest gate until 6/15? Valid vote options are Yes, No. 18:25:00 Vote using '#vote OPTION'. Only your last vote counts. 18:25:06 #vote Yes 18:25:09 #vote yes 18:25:16 #vote yes 18:25:22 i wonder if it's case sensitive 18:25:32 we'll find out in a bit 18:25:38 * sputnik13 prods abitha and dkalleg 18:25:41 vote 18:25:47 #vote Yes 18:25:49 #vote yes 18:25:55 #endvote 18:25:56 Voted on "Postpone decision on tempest gate until 6/15?" Results are 18:25:57 Yes (5): dkalleg, vipul, sputnik13, davideagnello, abitha 18:26:05 w00t 18:26:10 landslide 18:26:12 ok, cool, it's like all official like 18:26:14 :-D 18:26:32 ok, should we go on to the next topic? 18:26:41 +1 18:26:51 just got notice from openstack-infra that they would like a Cue core to review and +1 patch before they merge 18:27:01 #agreed follow up on tempest gate status 6/15 and decide whether to make it voting 18:27:03 for rally ci job 18:27:24 davideagnello: ok, action for vipul and me 18:27:40 #action vipul and sputnik13 to review https://review.openstack.org/#/c/187620/ and +1 it 18:28:05 #topic sputnik13 vipul davideagnello esmute start classifying undecided bugs 18:28:29 I checked undecided for bugs last night and at least as of last night there were no undecided bugs so that's good 18:29:04 so that means everything reported is an actual bug 18:29:19 I see three which don't seem to be classified 18:29:23 hmm, wait there's 3 that are undecided still 18:29:28 https://bugs.launchpad.net/cue 18:29:32 yeah 18:29:40 there's something wrong with the filter I used I guess 18:29:42 user error 18:30:21 #action esmute to classify https://bugs.launchpad.net/cue/+bug/1439329 and https://bugs.launchpad.net/cue/+bug/1439330 18:30:22 Launchpad bug 1439329 in Cue "Cluster goes to ERROR when creating it with flavor passed by name" [Undecided,New] 18:30:23 Launchpad bug 1439330 in Cue "Cannot delete cluster by name" [Undecided,New] 18:30:45 #action sputnik13 to harass josh barry to classify https://bugs.launchpad.net/cue/+bug/1450931 18:30:46 Launchpad bug 1450931 in Cue "Readme doc link incorrect" [Undecided,New] 18:30:57 actually that last one is probably just low 18:31:06 I'll follow up 18:32:12 next topic 18:32:14 ? 18:32:49 #topic blueprints 18:33:13 we have an agreement to create more blueprints to better document the features that are being worked on 18:33:34 #link https://blueprints.launchpad.net/cue 18:33:47 Thanks davideagnello for entering some of the blueprints 18:34:18 np, they are a start. we might want to add more as we see fit to each 18:34:30 +1 18:34:43 we should add more detail to each as we find more detail 18:35:14 agreed 18:35:15 I will be looking in to kafka for an "intro to kafka" thing I'm going to be doing next week, so I will take that one on 18:35:31 #action sputnik13 to fill in details for https://blueprints.launchpad.net/cue/+spec/kafka 18:36:04 can someone add some detail to https://blueprints.launchpad.net/cue/+spec/rally-scenario-tests 18:36:11 based on what we have and what's in process? 18:36:19 I can do that one 18:36:45 davideagnello can you also add a linke to the API in the v1-api blueprint? 18:37:19 #action davideagnello to add detail to https://blueprints.launchpad.net/cue/+spec/rally-scenario-tests based on existing rally tests and gate testing things in process 18:37:38 #action davideagnello to add link and information to v1 API in https://blueprints.launchpad.net/cue/+spec/v1-api 18:37:53 the others we can fill in details as we start tackling them 18:38:36 next on the agenda is/are bugs, should we go on or are there other things related to blueprints we need to discuss? 18:38:40 sputnik13: ok 18:38:53 sputnik13: to the API read the docs? 18:39:15 davideagnello yup, and as I recall there was a wiki page that was created a while back describing the API as well wasn't there? 18:39:27 a link to that would be good too for posterity 18:39:31 yes, created that one a while back 18:39:34 ok 18:40:27 we have 20 minutes left and I would like to leave some time in the end for open discussion, so let's move on if there aren't other things to discuss regarding blueprint 18:40:40 going once 18:40:44 going twice 18:40:47 I think that's all regarding blueprints, we should discuss which bugs 18:40:56 cool 18:40:58 should be resolved next 18:41:14 #topic bugs 18:41:23 #link https://bugs.launchpad.net/cue/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.importance%3Alist=CRITICAL&field.importance%3Alist=HIGH&field.importance%3Alist=MEDIUM&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_comb 18:41:23 inator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search 18:41:31 woah that doesn't work 18:42:12 #link http://bit.ly/1MChDwJ 18:43:11 vipul and I have the ongoing action to triage/disposition bugs, but I feel like a bug should not stay in the New state for any longer than a week 18:43:26 I think our current failure in reverting a flow on create is something that should be addressed 18:43:26 especially if they're critical, high, or medium 18:43:50 so I'd like to make sure we get the highest ones triaged and assigned 18:44:08 some of these actually need to be recategorized as far as importance 18:44:22 yes 18:44:22 as they don't follow the definition we agreed to 18:44:34 nic argument should be a list is already fixed. why is it still showing new? 18:45:06 abitha: status is changed when someone goes and changes it 18:45:20 when you commit things in gerrit, gerrit goes and updates the status for you 18:45:33 perhaps the bug wasn't properly referenced in the patch? 18:45:35 oh ok. 18:46:04 it is listed as partial-bug as the other half is fixed by the client 18:46:11 abitha: since you know where it was fixed, can you go update that? 18:46:18 ok 18:46:29 does the client say closes or partial-bug? 18:46:33 should I change the bug from partial to closes bug? 18:46:39 I think at least one change needs to say closes bug 18:46:49 but if the change was already merged I'm not sure you can update the commit message 18:46:50 oh ok. I will change and close this one 18:47:11 if thats the case can I close it manually? 18:47:20 so if the changes were already merged, just go ahead and change the status to fix committed and reference the changes (if they're not in the history already) 18:47:36 ok .will do 18:47:48 I only see one message from gerrit in the history, so you might have to add a link to the other one 18:48:05 sure 18:48:53 davideagnello: do you see the bug that states rollback isn't happening? 18:49:57 actually client patch already has closes-bug. but don't know why it wasn't linked correctly? 18:49:57 sputnik13: I don't see that one 18:50:49 davideagnello: I think I might have been conflating that bug with others like https://bugs.launchpad.net/cue/+bug/1452958 https://bugs.launchpad.net/cue/+bug/1452959 https://bugs.launchpad.net/cue/+bug/1452990 18:50:51 Launchpad bug 1452958 in Cue "cluster does not change to ERROR state when VM does not go ACTIVE" [High,New] 18:50:51 in my mind 18:50:52 Launchpad bug 1452959 in Cue "cluster does not ERROR on missing broker metadata" [High,New] 18:50:53 Launchpad bug 1452990 in Cue "resources not cleaned up when deleting a cluster in BUILDING state" [Medium,New] 18:51:15 so we might have to file it as a distinct bug 18:51:31 we should look in to it further 18:51:36 I agree it needs to be resolved soon 18:52:02 yes, those look like the results of a rollback not working 18:52:10 we can't go through all of the bugs during the meeting, can everyone go through the bugs they filed and make sure they're currently classified correct? 18:52:27 davideagnello: I disagree a bit, some of those should trigger the rollback 18:53:02 no wait, nevermind you're right 18:53:10 they're probably all related to the rollback not happening 18:53:18 we set ERROR status at the end of a rollback right? 18:53:24 yup, that's what I meant 18:53:27 yes we do 18:53:32 yeah, you're right 18:53:48 if the rollback reaches the first task :) 18:53:58 we need a way to reproduce the lack of rollback, I think I know how to do that 18:54:12 I'll reproduce the error and file a new bug 18:54:28 ok, how do you trigger that behavior? 18:54:35 make a task implicitly fail? 18:54:49 #action sputnik13 reproduce bug that fails to rollback a cluster create and file a bug with the details 18:55:09 davideagnello based on what I saw in the rally tests, running out of resources seems to trigger this 18:55:20 so I'm going to just create clusters until it fails 18:55:33 and make sure it does that reliably 18:55:45 ok, makes sense 18:56:12 #action vipul davideagnello esmute abitha dkalleg to check that existing bugs have the correct classification 18:56:53 the action last week was to make sure there were no Undecided bugs but several bugs that were already classified had improper classifications 18:57:27 we have 3 minutes left in the meeting :( 18:57:53 so in future meetings I'm hoping we can discuss the critical/high/medium bugs, but I don't think we have a clear picture of what those are right now 18:58:00 given there are some bugs that are mis-classified 18:59:28 questions? concerns? other topics? 18:59:34 ok, agreed 18:59:44 #topic Open Discussion 19:00:07 who's sick of the sun? 19:00:08 :) 19:00:16 so hot this past weekend 19:00:30 it was actually cooler in San Diego than Seattle 19:00:54 my wife actually started getting excited at the prospect of rain next week 19:00:54 :) 19:00:55 That doesn't make it hot :-P You want hot go check out Virginia in the summer. 19:01:13 actually, I think Abitha might trump us all 19:01:22 can we wrap up for the next meeting? 19:01:37 alrighty, thanks everyone 19:01:39 #endmeeting