Greetings,
We recently found a bug in the Nova-Glance interaction that prevents
booting snapshots using Glance's V2 API. The bug is that Nova creates
the snapshot and sets the ramdisk_id/kernel_id to None when it's not
available.
While this was ok in V1, it causes a failure for V2 since the
-Original Message-
From: Flavio Percoco [mailto:fla...@redhat.com]
Sent: Tuesday, July 28, 2015 3:15 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [nova][glance][stable] Stable exception for bug
#1447215: Allow ramdisk/kernel_id to be None
Greetings,
We
+1. Our production system hit this on Juno - Kilo upgrade.
Thanks,
Kevin
From: Flavio Percoco [fla...@redhat.com]
Sent: Tuesday, July 28, 2015 7:15 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [nova][glance][stable] Stable exception
On 7/28/2015 9:24 AM, Kuvaja, Erno wrote:
-Original Message-
From: Flavio Percoco [mailto:fla...@redhat.com]
Sent: Tuesday, July 28, 2015 3:15 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [nova][glance][stable] Stable exception for bug
#1447215: Allow ramdisk
On 07/28/2015 01:39 PM, Matt Riedemann wrote:
snip
Nova doesn't support glance v2 in kilo or liberty, so does it matter to
nova if this is in stable/kilo or not? Doesn't seem like it. This is a
barrier to getting glance v2 support into nova in mitaka though it seems.
It matters for the
