16:30:07 #startmeeting NovaBugScrub 16:30:08 Meeting started Wed Mar 12 16:30:07 2014 UTC and is due to finish in 60 minutes. The chair is tjones. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:30:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:30:11 The meeting name has been set to 'novabugscrub' 16:30:28 Hi - anyone here today? 16:31:03 *listens to crickets* 16:31:08 tjones: hi 16:31:21 just joined! 16:31:21 hello 16:31:26 phew - thought i was all alone today 16:31:31 heh 16:31:33 with the time change - i was confused 16:32:03 #topic tagging 16:32:04 yeah, this week is crazy, as here in EU we're still on winter time 16:32:09 lets do tagging first 16:32:21 we have 29 16:32:28 #link https://bugs.launchpad.net/nova/+bug/1285288 16:32:35 not sure if this is testing or docs? 16:33:00 and the last comment says it does not affect ci - so ??? 16:34:15 ideas? 16:34:31 maybe its fixed now? not sure 16:34:40 me either 16:34:44 i'll comment and close? 16:34:45 looks like something wrong with test dependency version? 16:35:20 needs more info maybe, like, does it still break? 16:35:33 ok incomplete and commented 16:35:58 #link https://bugs.launchpad.net/nova/+bug/1286257 16:36:11 libvirt 16:36:19 (struggling with train network, but here) 16:36:44 #link https://bugs.launchpad.net/nova/+bug/1286297 16:37:29 fix already proposed 16:37:47 no idea where to put this…. conductor? 16:38:14 fix is in dashboards…. so console? 16:41:33 im moving on in the interest of time. #link https://bugs.launchpad.net/nova/+bug/1286297 16:41:37 it seems we need a category for horizon 16:41:45 but, compute might do just as well 16:41:57 wendar: would console fit the bill? 16:42:09 I thought compute 16:42:19 console is for nova-console 16:42:28 ok compute it is 16:42:52 and, whoever looks at this will have to dig down into compute, so... yeah, makes sense 16:42:58 next one looks like volume to me https://bugs.launchpad.net/nova/+bug/1286297 16:43:08 isn't that the same one again? 16:43:18 https://bugs.launchpad.net/nova/+bug/1287622 16:43:20 heh 16:43:24 sorry 16:44:03 I agree volumes 16:44:20 #link https://bugs.launchpad.net/nova/+bug/1288214 - guessing cells 16:45:08 api 16:45:26 melwitt: not cells? just learning 16:46:17 ah - i see the log line attach the Nova API 16:47:12 ok next one does look to me like we need a horizon tag #link https://bugs.launchpad.net/nova/+bug/1288230 16:48:11 could be compute, with an "affects" for Horizon 16:48:44 done 16:49:04 this one i thought network but now i am thinking compute #link https://bugs.launchpad.net/nova/+bug/1288392 16:49:27 compute not handling neutron outtage nicely 16:49:36 I think compute too 16:49:58 #link https://bugs.launchpad.net/nova/+bug/1288609 16:50:04 network 16:50:47 #link https://bugs.launchpad.net/nova/+bug/1288700 16:51:22 this one is odd 16:53:24 compute or api? 16:54:07 almost looks like a wierd env issue 16:54:15 i'll put compute i guess 16:54:29 its api I think 16:54:40 you can put api too. error is coming from api log 16:54:46 sounds like its not doing some checking for Non correctly 16:54:54 or api code 16:54:55 ok put them both 16:55:18 #link https://bugs.launchpad.net/nova/+bug/1289036 16:56:05 again thought network but think now compute 16:56:09 compute probably 16:56:25 #link https://bugs.launchpad.net/nova/+bug/1289135 16:56:26 I'd go for compute 16:56:26 volumes 16:56:33 or api 16:56:40 for the one above 16:56:44 (time delay, that was for #1289036) 16:56:53 1289036 is libvirt I think 16:57:08 fails to unplug, then blows up 16:57:11 api 16:57:55 oops - https://bugs.launchpad.net/nova/+bug/1289135 16:57:56 vmware 16:58:06 blush 16:58:10 thought i already got those 16:58:30 #link https://bugs.launchpad.net/nova/+bug/1290362 16:58:39 libvirt 16:59:02 #link https://bugs.launchpad.net/nova/+bug/1290362 16:59:18 volumes 16:59:39 lets pause a minute and talk abut RC bugs 16:59:54 nods 16:59:58 i didn't do anything about scheduling more of these meetings - i didn't get any response at all from the ML 17:00:14 #link https://blueprints.launchpad.net/nova/+milestone/icehouse-rc1 17:00:21 RC bugs don't look terribly bad (to me) 17:00:36 there are 14 and they seem to be moving 17:01:23 i don't have timestamps on them (need to run my script) but perhaps this can be managed simply by pinging the owners if they are not moving them along 17:01:40 thoughts? 17:04:25 you mean your script checks the time since gerrit review associated with bug was updated or? 17:04:37 yes 17:04:49 russellb has been checking on those and keeping the list short 17:05:10 is there anything that i can do in addition to help him out? 17:05:13 I do wonder if there are any critical issue that we don't know about, but have been reported 17:05:25 but not seen anything myself 17:06:00 IMO we have to depend on the tag owners of the tags to bring that to our attention by prioritizing correctly. 17:06:12 that bug about the hypervisor list not working could be one of those 17:06:26 tjones: do the tag owners know they are meant to be doing that? 17:06:44 i did tell them in the ML - but i could send them a personal message ;-) 17:06:57 the ML has _a lot_ of traffic 17:07:15 yes - very true 17:07:29 i'll send a personal message - then we know they know 17:08:00 I've been out sick the past week since last meeting, so I'll be going through my tags 17:08:11 hope you are better 17:08:17 I am, thanks 17:09:30 ok - 12 more - shall we continue knocking them out? 17:09:50 I've got 30 more minutes free 17:09:59 im doing 2 meetings at once ;-) 17:10:05 :) 17:10:14 #link https://bugs.launchpad.net/nova/+bug/1290642 17:10:45 test issue ? 17:10:55 i mean an issue with the way the tests are written? 17:11:37 testing is a good place to start 17:11:55 it'll require some confirmation, and may be bounced to compute or something else 17:12:02 ja 17:12:13 #link https://bugs.launchpad.net/nova/+bug/1290660 17:12:24 db 17:12:33 yeah 17:12:44 #link https://bugs.launchpad.net/nova/+bug/1290767 17:12:45 network 17:13:12 or compute 17:13:18 maybe api? 17:13:23 lol 17:13:34 it's not a bug in neutron 17:13:48 but, the api needs some error code handling to retry? 17:13:55 sounds right 17:14:02 #link https://bugs.launchpad.net/nova/+bug/1290772 17:14:21 not sure what matchmaker is 17:14:35 it's a zeromq thing I thought 17:14:35 maybe console 17:14:59 console and conductor 17:15:13 they're affected by it, anyway 17:15:14 ok trying that 17:15:39 #link https://bugs.launchpad.net/nova/+bug/1291100 17:16:06 uh oh - regression? 17:16:30 maybe something we need to have in rc? 17:16:35 ruh-roh 17:17:07 yeah, worth raising for russellb's review 17:17:12 #action bring https://bugs.launchpad.net/nova/+bug/1291100 to russell's attention 17:17:19 also, compute 17:17:36 #link https://bugs.launchpad.net/nova/+bug/1291100 17:17:45 sorry 17:17:46 https://bugs.launchpad.net/nova/+bug/1291127 17:18:07 volumes 17:18:25 yep 17:18:29 #link https://bugs.launchpad.net/nova/+bug/1291163 17:18:44 libvirt 17:19:03 nods 17:19:09 that's not a valid mac addr 17:19:13 is it? 17:19:25 it's really, really not 17:19:29 yeah 17:19:35 so ?? invalid 17:20:16 Yeah, if the reporter has some additional information they can respond to the invalid. 17:20:24 yeah ok 17:20:43 #link https://bugs.launchpad.net/nova/+bug/1291246 17:20:50 well, seems like neutron should validate the max 17:20:51 here's another we may want to show russell 17:20:52 mac 17:21:05 johnthetubaguy1: true - could be a nicer error msg 17:21:20 tjones: well, port create should fail I think 17:21:35 he's saying neutron allows creation of a port with '123' mac address but then nova can't use it. which is not a nova problem imo 17:21:56 right, its a neutron error checking issue 17:21:59 and agree 17:22:09 ok back to neutron and reopened 17:22:10 I mean api validation, but you get the idea 17:22:24 yes 17:22:26 yeah 17:22:41 fair enough, but more a feature request than a bug, so probably next cycle 17:22:45 back to the race - https://bugs.launchpad.net/nova/+bug/1291246 17:22:52 1291246 is nothing new really 17:23:21 oh hang on 17:23:27 maybe they forgot the correct value here 17:24:23 compute I guess 17:24:39 its a db thing really, well an objects and db thing 17:24:46 or api. not sure where this code is. oh 17:25:07 so objects db and api? 17:25:18 just objects and db 17:25:36 TWO MORE 17:25:44 #link https://bugs.launchpad.net/nova/+bug/1291471 17:26:01 volume 17:26:13 whoot! (2 more) 17:26:26 and, agreed 17:26:31 #link https://bugs.launchpad.net/nova/+bug/1291489 17:26:37 network 17:26:56 or api 17:27:16 leaning toward api 17:27:23 me too 17:27:35 same 17:27:46 ok we are DONE with tagging 17:27:55 huzzah! 17:28:12 the only bug we think may be a rc candidate is https://bugs.launchpad.net/nova/+bug/1291100 17:28:45 what about the objects and db thing 17:28:49 anything else we can/should do to help with rc bugs other than my sending a personal note to each tag owner making sure they know they need to raise up critical bugs? 17:29:13 we may want to review the tags with no owners in this group 17:29:19 (next week) 17:29:28 ok tags with no owners is HUGE 17:29:43 i have a speadsheet i can share (google doc) with you 17:29:58 i need to scrub it some more - but it is daunting 17:30:06 looks like all the official tags have owners now, that's good 17:30:11 yes they do 17:30:34 well done, tjones :) 17:30:47 i have a list of bugs with no official tag on them that we can go over - maybe start by date opened (earliest 1st) 17:30:53 and, sure I'd be happy to look over the spreadsheet 17:31:11 it'll give me some focus for between-meeting triage 17:31:17 wendar: thanks. I'll send it to you folks. anything else today? 17:31:35 i should really attend this other meeting but i wanted to get through this list today 17:31:49 off you go, then 17:31:50 #action send out bugs with no official tags list 17:31:51 and thanks! 17:31:53 #endmeeting