[Bug 1298061] Re: nova should allow evacuate for an instance in the Error state
Brian Murray
brian at ubuntu.com
Thu Jan 26 19:27:38 UTC 2017
Hello Chris, or anyone else affected,
Accepted nova into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nova/1:2014.1.5-0ubuntu1.6 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: nova (Ubuntu Trusty)
Status: In Progress => Fix Committed
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1298061
Title:
nova should allow evacuate for an instance in the Error state
Status in Ubuntu Cloud Archive:
Fix Released
Status in Ubuntu Cloud Archive icehouse series:
In Progress
Status in OpenStack Compute (nova):
Fix Released
Status in nova package in Ubuntu:
Fix Released
Status in nova source package in Trusty:
Fix Committed
Bug description:
[Impact]
* Instances in error state cannot be evacuated.
[Test Case]
* nova evacuate <error_state_instance> <another_compute_host>
* nova refuses to evacuate the instance because of its state
[Regression Potential]
* 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:
https://bugs.launchpad.net/cloud-archive/+bug/1298061/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list