failed rescue should not error an instance
Bug #1170328 reported by
Matthew Sherborne
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Matthew Sherborne |
Bug Description
Currently if one attempts to put a VM into rescue mode and the operation fails. The VM is set to vm_state.ERROR.
As a customer/end user, if I attempt to put my VM in rescue mode and it fails, I would like it to stay in ACTIVE mode so that I can pursue other repair options, such as reboot or migrate.
If it's in ERROR status, only someone with admin api access can get it out again. For me (the end user) that means more down time while I find an admin to help me.
----
If a rescue attempt fails, the VM's state should return to what it was before the rescue attempt started, and the user should be notified of the failure.
Changed in nova: | |
assignee: | nobody → Matthew Sherborne (msherborne+openstack) |
status: | New → In Progress |
description: | updated |
description: | updated |
description: | updated |
Changed in nova: | |
milestone: | none → havana-1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | havana-1 → 2013.2 |
To post a comment you must log in.
This undoes half of https:/ /bugs.launchpad .net/nova/ +bug/919444
In that bug, they say, if we fail to UNrescue an instance, it should be put into error state.
However the implementation also puts it into error state if a rescue attempt fails.
If a rescue attempt fails, it should revert the instance back to it's original state.