[Openstack] Nova boot from volume problem after Kilo upgrade
David Medberry
openstack at medberry.net
Wed Aug 26 17:21:32 UTC 2015
Seen similar issues.
There are some known glance issues and also so nova filter issues going on
by default.
I'd look at enabling "verbose=True" in Nova and seeing if you can get
closer to the truth of what's going on and then tail the nova logs. We've
put that down in our runbooks as a best practice for debugging this.
The slides on our talk have more info:
http://j.mp/oskilo_twc
and I'll be adding another today.
(Our issue was kind of around glance api v1 and v2 differences and missing
descriptions among other things. Other issues also plagued the upgrade.)
See slides 8&9 and 12 and probably soon a 13.
On Wed, Aug 26, 2015 at 10:59 AM, Jonathan Proulx <jon at jonproulx.com> wrote:
> Hi All,
>
> Before I open a bug...
>
> after Kilo upgrade I get 'Error: Flavor's disk is too small for
> requested image' when trying to boot from cinder volumes that are
> larger than the image-type root volume.
>
> This is a severe issue for me. Has anyone else seen/reported this (I
> didn't see it looking at the BTS but may have missed it)
>
> Anyone have a work around other than duplicating all my existing
> flavors with a root size of '0' which would be a mess and confuse the
> hell out of my users.
>
> -Jon
>
> ps. instance types are stupid & users should be able to specify
> resources (within bounds) anyway but that's a longer argument and much
> harder fix :)
>
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack at lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20150826/bf031ba5/attachment.html>
More information about the Openstack
mailing list