Reviewed: https://review.openstack.org/367772
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=97ce9e5e8b985926e338ba4fd63ff7c7065356c8
Submitter: Jenkins
Branch: master
commit 97ce9e5e8b985926e338ba4fd63ff7c7065356c8
Author: Gary Kotton <gkot...@vmware.com>
Date: Thu Sep 8 23:53:02 2016 -0700
Compute: ensure that InvalidDiskFormat is handled correctly
In the event that a hypervisor does not support a specific disk format
it will raise an exception InvalidDiskFormat. In this circumstance
the instance was being stuck in 'SCHEDULING' state.
When a exception like this is encountered we will treat it similarly
to the ImageUnacceptable and InvalidDiskInfo execptions.
Change-Id: I61ed418e3884c773df87718d13fef6f69010342b
Closes-bug: #1621564
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1621564
Title:
Neutron port is not deleted after instance is deleted
Status in OpenStack Compute (nova):
Fix Released
Bug description:
For some reason, instance can be stuck in scheduling or error state,
e.g. incompatible image, lack of property in image. In this case, the
neutron port is not deleted after instance has been deleted.
This happens with recent trunk. By default, devstack creates a KVM
image without --property hypervisor_type=qemu. Instance boot with this
image is stuck in scheduling state. Port is still there after delete
this instance.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1621564/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
