Re: [openstack-dev] [nova][glance][stable] Stable exception for bug #1447215: Allow ramdisk/kernel_id to be None
On 07/28/2015 01:39 PM, Matt Riedemann wrote: > > 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 following reason. If you create an image via Nova in Kilo (image proxy, snapshot, etc), that image is not accessible over glance v2 (which is the default for glanceclient in the kilo timeframe). It just explodes instead. I'd consider this pretty critical failure of compatibility between v2 and v1 in glance. It also points at a missing set of test cases which is to create images via 1 API and be able to access them over the other. I don't know if that is in process or not, but it would be really good to deliver those test cases as part of this work. -Sean -- Sean Dague http://dague.net __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova][glance][stable] Stable exception for bug #1447215: Allow ramdisk/kernel_id to be None
+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 for bug #1447215: Allow ramdisk/kernel_id to be None 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 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 found. 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/ Cheers, Flavio -- @flaper87 Flavio Percoco __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova][glance][stable] Stable exception for bug #1447215: Allow ramdisk/kernel_id to be None
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/kernel_id to be None 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 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 found. 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. +1 In my understanding as well we would be backwards compatible and this would make the future upgrades so much easier in the case nova starts consuming v2 Image API. - Erno The change proposed is to allow these fields to be None. The review: https://review.openstack.org/#/c/205432/ Cheers, Flavio -- @flaper87 Flavio Percoco __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 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. -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova][glance][stable] Stable exception for bug #1447215: Allow ramdisk/kernel_id to be None
> -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 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 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 found. > > 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. +1 In my understanding as well we would be backwards compatible and this would make the future upgrades so much easier in the case nova starts consuming v2 Image API. - Erno > > The change proposed is to allow these fields to be None. > > The review: https://review.openstack.org/#/c/205432/ > > Cheers, > Flavio > > -- > @flaper87 > Flavio Percoco __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova][glance][stable] Stable exception for bug #1447215: Allow ramdisk/kernel_id to be None
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 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 found. 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/ Cheers, Flavio -- @flaper87 Flavio Percoco pgpLJLj9mYSWg.pgp Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
