16:30:42 #startmeeting novabugscrub 16:30:43 Meeting started Wed Jun 11 16:30:42 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:44 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:30:46 The meeting name has been set to 'novabugscrub' 16:30:52 hi anyone around? 16:30:57 o/ 16:31:03 hey wendar 16:31:11 hi 16:31:27 thanks for helping. i did the obvious tags this am 16:31:34 excellent 16:31:36 #link https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW 16:31:42 left with a couple 16:32:01 #link https://bugs.launchpad.net/nova/+bug/1326566 16:33:07 1st i thought compute, but now im thinking network as it is failing in the network cleanup code 16:33:53 hmmmm... it's one of those cascading problems 16:33:57 yeah 16:34:26 well the 1st prob is handled properly by compute, but the cleanup is failing 16:34:51 like, something needs to abort after the first error, but is trying to proceed normally 16:35:05 hmmm - then is could still be compute 16:35:45 it's in ovs 16:36:05 sorry, came in late, what bug is this? 16:36:10 (that was a ...) 16:36:12 https://bugs.launchpad.net/nova/+bug/1326566 16:36:28 so networking then?? 16:36:38 * kashyap here 16:36:44 hey kashyap 16:37:23 tjones, I'm currently going through NEW bugs - https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 16:37:48 And, tag appropriate stuff, mostly I'll keep an eye on libvirt stuff but can try others too 16:37:51 tjones: yeah, I'd go with networking 16:38:01 we are just tagging a couple of remianing bugs so the subteam owners can take the next pass 16:38:20 tjones, Also, libvirt tag for the above bug 16:38:36 ok done 16:38:43 #link https://bugs.launchpad.net/nova/+bug/1326599 16:39:04 oslo??? 16:39:41 tjones: or api? 16:39:55 really no idea 16:39:58 Yeah, api, looking at the fix 16:40:01 and Nova 16:40:06 * mriedem joins late 16:40:20 hi mriedem we are on https://bugs.launchpad.net/nova/+bug/1326599 16:40:28 api and nova 16:40:41 tag with api 16:40:41 well everything is nova ;-) 16:40:45 seems like network is the appropriate tag for that guy 16:40:52 kenichi opened it so he probably knows the isue 16:41:02 #link https://bugs.launchpad.net/nova/+bug/1326901 16:41:58 conductor 16:42:06 yup 16:42:12 #link FYI - https://wiki.openstack.org/wiki/Bug_Tags#Nova 16:42:44 #link https://bugs.launchpad.net/nova/+bug/1327028 16:43:03 for https://bugs.launchpad.net/nova/+bug/1326901 i asked what release they are on 16:43:14 those details are usually lacking 16:43:21 yeah good idea 16:43:32 "shit blows up, please figure it out..." 16:43:37 lol 16:43:37 :-) 16:43:54 Also, this bug looks woefully short of info -- https://bugs.launchpad.net/nova/+bug/1327028 16:43:54 next one seems like api but really an opinion 16:44:02 yes that is the one 16:44:30 yeah, ask for more info, which API is used, which release are they on, what is the request and response, etc 16:44:48 done 16:45:02 #link https://bugs.launchpad.net/nova/+bug/1327406 16:45:19 tjones: marked that previous one as incomplete 16:45:27 mriedem: good idea 16:45:29 * kashyap wrote this wiki page a while ago -- https://wiki.openstack.org/wiki/BugFilingRecommendations 16:45:38 Should probably stick it in most bugs I try to triage 16:46:02 now this next one is networking. kashyap great! i'll start adding that when there is not enough info 16:47:08 #link https://bugs.launchpad.net/nova/+bug/1328367 16:47:47 hold up a sec 16:47:52 https://bugs.launchpad.net/nova/+bug/1327406 16:48:09 there was a patch for nova so status changed to in progress and assigned the owern 16:48:11 *owner 16:48:13 also tagged with network 16:48:31 i just tagged with network 16:48:47 this is my first nova bug meeting, but are we not going through the bugs like that in detail? or is this just quickly tagging things? 16:49:12 well this one has a proposed patch - so i was quickly moving over it 16:49:17 mriedem: we're doing quick triage 16:49:49 the purpose is to get things in the column owners awareness - they may not see untagged bugs 16:50:01 essentially, making sure the bugs are raised to the attention of the folks who have agreed to own a particular tag space 16:50:05 are the column owners actually looking at them though? 16:50:11 mriedem, They ought to be gone over in detail, I try my best to find root-cause and post deails 16:50:29 some are some are not. i try to send a nag email every once in a while 16:50:54 1328367 I'm leaning toward compute 16:51:31 wendar: ok makes sense 16:51:42 also tag with resize and/or migration 16:51:44 or migrate 16:51:55 i've been trying to tag resize/migrate bugs also 16:52:12 niether of those are official tags - should we add that to the list? 16:52:28 * kashyap is still to do a resize test of Nova instance in multi-node setup to reconfirm a certain bug 16:52:50 just something i've been doing 16:52:50 tjones, Yeah, I was wondering _who_ blesses them as "official" tags 16:52:53 compute tag is very broad 16:53:02 mikal is the blesser of tags 16:53:04 True, doesn't mean anything 16:53:25 resize seems to be a particularly nasty thing for bugs we get 16:53:31 the significant difference is whether anyone is watching the tag 16:53:32 in part b/c we don't have multi-node tempest testing in the gate 16:53:44 so, if mriedem wants to watch resize or migration, I say add it 16:53:44 i think it's useful for finding duplicates though 16:53:49 i don't want to watch it 16:53:53 but i don't want 20 duplicates 16:53:55 Uh, yeah. I admit twice I attempted to reproduce a nasty resize bug, got distracted and did something else 16:53:57 b/c it's not tested upstream 16:54:05 i think we should spend some time in portland talking about this stuff. 16:54:10 tjones: it's on the agenda 16:54:14 yep 16:54:20 and the reason i am going ;-) 16:54:35 ok last untagged one is https://bugs.launchpad.net/nova/+bug/1328966 16:54:40 but my point is, until we have multi-node resize/migrate testing in the gate, we can sub-tag these for compute to avoid duplicates hopefully 16:55:06 Exactly, the bug I was testing works fine in a single node allinone style setup, but blows up in a 2-node setup 16:55:15 api 16:55:36 duh 16:55:43 i guess i ran out of time on that one 16:56:01 or, it came in 43 minutes ago :) 16:56:13 lol 16:56:30 tjones: i talked to him about that this morning in nova 16:56:35 it's triaged 16:56:37 tag with api 16:56:49 folks - this wiki shows the offical tags and has links to untriaged. if you are a tag owner then please take a look at your column https://wiki.openstack.org/wiki/Nova/BugTriage 16:56:58 mriedem: i know - i just tagged it 16:57:25 there are 171 total untriaged bugs across all columns 16:57:35 https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 16:59:02 almost out of time. anyone have anything they want to discuss for 1 minute? 16:59:16 kashyap: i've added your wiki to my meeting page. thanks 16:59:16 bug day? 16:59:32 tjones, Sure, no worries. 16:59:36 well… it was mixed. some people did a lot, many people did not 17:00:22 i've got to go run another meeting. thanks all for helping out today 17:00:24 #endmeeting