[openstack-dev] [nova][glance][stable] Stable exception for bug #1447215: Allow ramdisk/kernel_id to be None
Fox, Kevin M
Kevin.Fox at pnnl.gov
Tue Jul 28 18:22:31 UTC 2015
+1. Our production system hit this on Juno -> Kilo upgrade.
From: Flavio Percoco [flavio at redhat.com]
Sent: Tuesday, July 28, 2015 7:15 AM
To: openstack-dev at lists.openstack.org
Subject: [openstack-dev] [nova][glance][stable] Stable exception for bug #1447215: Allow ramdisk/kernel_id to be None
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
While this was ok in V1, it causes a failure for V2 since the current
schema-properties file doesn't allow both fields to be None. The right
fix would be for Nova not to set these fields at all if no value is
Nonetheless, we have a workaround that would make this work. The
workaround landed in master and it's been proposed for kilo.
Therefore, I'm asking for a stable exception to merge this patch,
which is backwards compatible (unless I'm missing something). The
exception is being requested because it does change the API.
The change proposed is to allow these fields to be None.
The review: https://review.openstack.org/#/c/205432/
More information about the OpenStack-dev