16:30:44 #startmeeting Nova Bug Scrub 16:30:46 Meeting started Wed Mar 5 16:30:44 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:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:30:49 The meeting name has been set to 'nova_bug_scrub' 16:31:07 lets do a quick hello to see who is here 16:31:22 o\ 16:31:34 o/ 16:31:42 o/ 16:31:53 o/ 16:31:55 for the next 8 minutes (train) 16:32:09 o/ 16:32:10 ok lets start then ;-) 16:32:16 #topic triage owners 16:32:23 o/ 16:32:42 i didn't get any results from my ML request for owners on #link https://wiki.openstack.org/wiki/Nova/BugTriage 16:33:02 we still need console, ec2, scheduler, testing, and nova-manage 16:33:06 OK, I will take scheduler then 16:33:09 any ideas? 16:33:12 thanks johnthetubaguy 16:33:20 #action make johnthetubaguy the scheduler owner 16:33:52 it's not in bad shape from an un-triaged point of view 16:34:04 jogo: do you fancy testing? 16:34:11 ones that are in bad shape are libvirt, networking, and testing ;-) 16:34:30 you can put me on nova-manage 16:34:48 i have kchamart as the owner of libvirt - but have not heard back from him/her 16:34:53 thanks melwitt1 16:35:03 OK… sounds like libvirt could do with extra people on that list 16:35:07 #action melwitt to be the owner of nova-manage 16:35:10 jogo: I'll help with testing if you want to take it, I just don't want to be primary on two 16:35:21 i can put you both ;-) 16:35:26 johnthetubaguy: not enough badwidth to do it right 16:35:32 bandwidth 16:35:43 let me ask one of our CI guys if they have bandwidth 16:35:47 jogo: no problem, just wanted to check ;-) you see so on top of that stuff 16:36:00 I am happy to help out with that but don't wnat to be primary either 16:36:02 #action see if someone can help wendar with testing 16:36:07 tjones: I started on both this week, but if anyone pops up for either, I'm happy to share 16:36:16 thanks wendar 16:36:32 so libvirt is really needing help 16:37:02 does anyone know if kchamart is still working on it? 16:38:12 ok - lets move on to tagging the last 26 unless someone has something they want to discuss? 16:38:34 tjones: no idea, russellb might be worth asking 16:38:53 just a quick question on how to tag feature tickets that are held for now because of feature freeze? 16:38:58 #action ask russellb who else can help with libvirt 16:39:35 wendar: im assuming the same as always - they would be help up in review if they are part of a BP 16:39:43 s/help/held 16:40:01 #topic bug tagging 16:40:15 #link https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW 16:40:37 * jogo gets off train 16:40:49 #link https://bugs.launchpad.net/nova/+bug/1279857 16:41:25 this is a feature request for guest debug logging 16:41:32 so…. compute? 16:41:44 sounds good 16:42:06 +1 16:42:21 #link https://bugs.launchpad.net/nova/+bug/1269407 16:42:33 network 16:42:57 yeah 16:43:06 #link https://bugs.launchpad.net/nova/+bug/1271479 16:43:29 does this belong to nova or horizon? 16:43:30 libvert? 16:43:46 oh ok 16:43:54 it sounds like horizon, no? 16:44:09 oh nvm, hard reboot doesn't work apparently 16:44:17 it sounds like horzon puts the right metadata but it is not honored 16:44:38 from the cli 16:44:40 #link https://bugs.launchpad.net/nova/+bug/1271479 16:44:42 tjones: but the cli works fine? 16:44:56 johnthetubaguy: melwitt - yes i read it the cli is fone 16:44:57 fine 16:45:40 then another comment says cli hard reboot doesn't work 16:46:51 right - confusing 16:47:15 ok leaving it with libvirt 16:47:40 #link https://bugs.launchpad.net/nova/+bug/1280033 16:48:03 no idea 16:48:20 oslo? 16:48:32 i think this is removing it from nova 16:48:40 each project is represented here... 16:48:47 yeah all projects need to update dependency 16:48:56 yeah 16:49:09 I'm never sure how to tag ones like that 16:49:14 yeah, doesn't need a tag I guess, unless we have a dependency one, seems silly 16:49:29 here is where we need "wat" 16:49:54 #action put "wat" back for bugs like https://bugs.launchpad.net/nova/+bug/1280033 16:50:04 maybe, "other" would be better? 16:50:04 and assign to russellb 16:50:06 :-D 16:50:18 oooh, the dreaded other 16:50:20 just needs the dependency list updating 16:50:28 how about a status other than New? 16:50:38 we have one, triaged? 16:50:52 triaged is a good idea 16:51:14 johnthetubaguy: well it could be we need a bucket for overall nova stuff. we can triage it but if it is not tagged im worried it will get lost 16:51:27 we have a TON of untagged bugs that are not New 16:51:38 I'd tag it with oslo, just because it's the kind of thing I'd do when working on other oslo stuff. 16:51:48 370 to be precise 16:51:58 ok will do 16:52:00 theoretically selecting all "triaged" should give a list of things we know how to fix that just need to get done 16:52:00 tjones: true, maybe other makes sense then? 16:53:06 well it sounds like wendar will take care of it if i put it in oslo ;-) 16:53:21 true :) 16:53:41 getting close to time - so moving to #link https://bugs.launchpad.net/nova/+bug/1280389 16:54:25 network? 16:54:28 yeah 16:54:47 #link https://bugs.launchpad.net/nova/+bug/1281087 16:54:50 migration bug 16:55:07 compute? 16:55:33 yeah #link https://bugs.launchpad.net/nova/+bug/1281969 16:55:43 the possible dupe in the comment is tagged libvirt fwiw 16:56:04 #action look at the dup comment in https://bugs.launchpad.net/nova/+bug/1281087 16:56:28 this one https://bugs.launchpad.net/nova/+bug/1281969 looks like an infra issue 16:57:02 I'd say api probably 16:57:34 needs more info I feel 16:57:41 need nova logs for the error 16:58:09 ok added that comment 16:58:14 nova returning 500 to tempest, could be compute too 16:58:49 once we get more info we can triage it better. 16:59:12 or i can put both? 16:59:25 never mind - they can't do anything without the nova logs 16:59:34 almost out of time. 16:59:38 does that get an Incomplete? 16:59:42 should i change this to 8am-9am? 16:59:47 wendar: good idea 16:59:56 start it 1/2 hour earlier? 17:00:05 yeah, can ask the reporter for additional info then mark incomplete until they reply 17:00:23 1/2 hour earlier is fine for me 17:00:27 so is running 1/2 hour longer 17:00:29 I can't make half an hour earlier I am afraid, at least, probably not 17:00:35 i have another meeting now 17:00:37 but I can just join late 17:01:07 cause things are just going to heat up for the next couple of weeks 17:01:18 we will need to start focusing on movement of critical bugs for rc 17:01:26 not just tagging 17:01:29 yeah 17:02:12 10 minutes per day might be more effective for a couple weeks than 1 hour per week 17:02:17 but, difficult to coordinate 17:02:27 interesting... 17:02:27 (and definitely not sustainable beyond a couple weeks anyway) 17:02:43 that is a really good idea 17:02:53 could be just focused on RC 17:03:02 yes 17:03:30 only up unitl rc ;-) 17:03:42 yeah 17:04:15 but the thing we need to spot it the big bloopers, so probably need to get the tag owners to pull their finger out with priority setting right? 17:04:41 johnthetubaguy: yes that is critcal (which is why i wanted owners so badly) 17:05:05 :) 17:06:32 let me think about how this will work and i'll drop an email to the ML 17:07:01 good idea 17:07:07 and i'll continue tagging the obvious ones. i gotta run to my next meeting. thanks for the help! 17:07:10 #endmeeting