[Bug 1298061] Update Released
brian at ubuntu.com
Thu Feb 2 22:04:48 UTC 2017
The verification of the Stable Release Update for nova has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
nova should allow evacuate for an instance in the Error state
Status in Ubuntu Cloud Archive:
Status in Ubuntu Cloud Archive icehouse series:
Status in OpenStack Compute (nova):
Status in nova package in Ubuntu:
Status in nova source package in Trusty:
* Instances in error state cannot be evacuated.
* nova evacuate <error_state_instance> <another_compute_host>
* nova refuses to evacuate the instance because of its state
* Cherry picked from upstream
- removed unnecessary argument passing
- add allowing ERROR state before evacuating.
* actually, in code, added one parameter, and removed unused one.
so very low regression possibility.
* Tested on juju+maas test env.
* Passed tempest smoke tests locally.
Note: one simple way to put an instance into error state is to
directly change its database record, for example "update instances set
vm_state='error' where uuid='XXXXXXXX'"
We currently allow reboot/rebuild/rescue for an instance in the Error
state if the instance has successfully booted at least once.
We should allow "evacuate" as well, since it is essentially a
"rebuild" on a different compute node.
This would be useful in a number of cases, in particular if an initial
evacuation attempt fails (putting the instance into the Error state).
To manage notifications about this bug go to:
More information about the Ubuntu-openstack-bugs