18:00:07 #startmeeting nova-bugs-team 18:00:07 Meeting started Tue Jun 28 18:00:07 2016 UTC and is due to finish in 60 minutes. The chair is markus_z. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:10 The meeting name has been set to 'nova_bugs_team' 18:00:49 hello everyone 18:00:54 anyone around? 18:02:08 * markus_z waits patiently 18:02:32 o/ 18:03:28 o/ 18:03:31 hey matt, I'll wait for a few more minutes to see if others join 18:03:44 hey auggy 18:04:20 Let me throw out some numbers meanwhile 18:04:22 hey markus_z sorry about that 18:04:29 #info 810 open bugs overall 18:04:38 #info 33 new untriaged bugs 18:05:00 auggy: no worries 18:05:31 I checked the reports yesterday and today for a short period. A lot of unnecessary reports IMO, more than usual, no idea why 18:06:05 i went through the stale incomplete bugs and got that down in the past couple weeks 18:06:33 ah, that's cool, thanks! I've seen some numbers decline there. 18:06:54 So, nothing really new from my side. We still have bugs... 18:07:05 Anyone an open item you want to discuss? 18:07:08 i have 2 bugs i came across that i wanted to bring attention to 18:07:28 the first is this one - https://bugs.launchpad.net/nova/+bug/1418187 18:07:28 Launchpad bug 1418187 in nova (Ubuntu) "_get_host_numa_topology assumes numa cell has memory" [Medium,Incomplete] 18:07:46 Nova is added there and has been in Incomplete for awhile 18:07:55 but it's not clear what info is needed from Nova to change the status 18:08:49 #action markus_z clarify with sahid what's up with https://bugs.launchpad.net/nova/+bug/1418187 18:08:49 Launchpad bug 1418187 in nova (Ubuntu) "_get_host_numa_topology assumes numa cell has memory" [Medium,Incomplete] 18:08:58 ok, what's the second one? 18:09:20 https://bugs.launchpad.net/nova/+bug/1064386 18:09:20 Launchpad bug 1064386 in OpenStack Compute (nova) "Image stays in Saving State if any error occurs while snapshotting an instance" [Medium,In progress] - Assigned to Prateek Arora (parora) 18:09:28 it looks like there is a fix proposed and it just needs reviews 18:09:33 Looking at the first one, I assume dims wanted to let that auto-expire, but that doesn't work if it has an assignee. 18:10:30 oh it looks like the author changed the status from Fix Committed to In Progress 18:10:38 which idk why they did that 18:11:20 Looks like she pushed a patch: https://review.openstack.org/#/c/294513/ 18:11:23 or wait idk, i'm just confused 18:11:55 yeah, it just looks like they did it right before the summit 18:12:18 but i just wanted to point it out as a bug fix that's there and could use some reviews, i'm not sure how else to bring it to people's attention 18:12:21 right, and a new ps 12 days ago 18:12:55 yeah i thought maybe launchpad wasn't showing it because closes bug was in the wrong place 18:12:59 i've had that happen sometimes 18:13:03 but for some reason it's not linking to the bug 18:13:17 they left a link to the patch in the bug report 18:13:20 I guess this week most people will focus on review non-prio-features 18:13:20 it got some reviews 18:13:30 it's a race so there are questions how to best deal with it 18:13:56 the recreate is the user deletes the instance while it's snapshotting 18:14:01 snapshooting? 18:14:19 oh i see, it's linked to a different bug 18:14:32 i wonder if those should be marked as duplicates.. 18:15:21 probably 18:15:29 1064386 was opened in 2012 18:16:30 sounds a little like a duplicate, yeah 18:16:40 the title of the new patch is even the same as the original patch https://review.openstack.org/#/c/24820/ 18:16:45 omg wow 18:17:26 it's mostly the same fix 18:17:31 the new one is in the compute api 18:17:36 the old one is in the manager 18:18:30 in the old patch they suggesting updating the image status to error, but i'm not sure that's possible 18:18:36 *suggested 18:19:38 the newer one in the api is a bit cleaner 18:19:42 since it doesn't catch all errors 18:19:58 ahh ok, that makes more sense 18:20:13 i think i was looking at this while waiting for the gate for my stuff and just didn't pay full attention to it ;) 18:22:00 i know this week is non-priority ff, so yeah no big deal but i think i just wanted to make sure this one didn't fall through the cracks 18:22:21 i went ahead and marked that other one as a duplicate of the one the patch is linked to 18:22:45 thanks for the explanation mriedem :) 18:23:10 cool cool :) 18:23:36 i reviewed it 18:23:37 -1 18:23:44 it's not a terrible fix, but needs some work 18:23:46 mriedem: do you think you could persuade one of the other cores to do the bug skimming for a week? 18:24:05 cores? do bug triage?! 18:24:07 It's mainly you, john and sean 18:24:16 sean is out for a few weeks i think 18:24:29 yeah he's at the leadership training thing and then on vacation after that 18:24:31 the core team is working on getting to the non-priority feature freeze 18:24:59 mriedem: yeah, this week would be bad, I see that, but maybe after the midcycle 18:25:04 markus_z: i'll mention something in the nova meeting 18:25:20 thanks 18:25:35 ok, anyone anything else? 18:25:59 that's all i had 18:26:04 ok, closing in 3... 18:26:25 thanks for your time, next meeting on next Tuesday, 8 UTC 18:26:31 thx 18:26:33 #endmeeting