diff options
| author | Phil Day <philip.day@hp.com> | 2013-06-08 00:30:18 +0100 |
|---|---|---|
| committer | Phil Day <philip.day@hp.com> | 2013-06-14 20:28:34 +0100 |
| commit | bd9269278a532468e81bc752f89f05d74d9ee8e5 (patch) | |
| tree | c9c608f5d199dce369595cae2f0c366af83fa83d /nova/utils.py | |
| parent | c9cb610b8f6dc1d8fda64f1eba1e2a1d9bf2c53a (diff) | |
| download | nova-bd9269278a532468e81bc752f89f05d74d9ee8e5.tar.gz nova-bd9269278a532468e81bc752f89f05d74d9ee8e5.tar.xz nova-bd9269278a532468e81bc752f89f05d74d9ee8e5.zip | |
Fix bad vm_state change in reboot_instance()
Currently reboot_instance() in the compute manager
changes the vm_state to active before it does anything
else. This means that if there is an error in the reboot
operation then the vm_state is left as active although
the instance may not be running.
This change leaves the vm_state alone until the reboot
has completed
If the reboot fails but the power_state shows that it
is running then we log the fault but leave it in an
active or rescued state
If the reboot fails and the power_state shows that it
is not running then we set vm_state to error
See also https://bugs.launchpad.net/nova/+bug/1183946
which make recovery from an Error state possible.
Fixes bug: 1188343
Change-Id: Idabd358d3bcaf63e21ff59188f805143dbaf9ada
Diffstat (limited to 'nova/utils.py')
0 files changed, 0 insertions, 0 deletions