| 2013-04-18 12:16:17 |
Matthew Sherborne |
bug |
|
|
added bug |
| 2013-04-18 12:16:30 |
Matthew Sherborne |
nova: assignee |
|
Matthew Sherborne (msherborne+openstack) |
|
| 2013-04-18 12:16:41 |
Matthew Sherborne |
nova: status |
New |
In Progress |
|
| 2013-04-18 12:26:28 |
Matthew Sherborne |
description |
When one attempts to put a VM into rescue mode and it fails, the instance state should be reverted, not put into vm_state.ERROR. |
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. |
|
| 2013-04-18 12:27:21 |
Matthew Sherborne |
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. |
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 |
|
| 2013-04-18 12:27:46 |
Matthew Sherborne |
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 |
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. |
|
| 2013-04-23 19:37:52 |
OpenStack Infra |
nova: status |
In Progress |
Fix Committed |
|
| 2013-05-29 10:21:17 |
Thierry Carrez |
nova: status |
Fix Committed |
Fix Released |
|
| 2013-05-29 10:21:17 |
Thierry Carrez |
nova: milestone |
|
havana-1 |
|
| 2013-10-17 11:39:57 |
Thierry Carrez |
nova: milestone |
havana-1 |
2013.2 |
|
