VM in rescue state must have a restricted set of actions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
Medium
|
Olga Gusarenko |
Bug Description
https:/
commit 8ff170dc95bf310
Author: Leandro I. Costantino <email address hidden>
Date: Mon May 19 19:58:47 2014 -0300
VM in rescue state must have a restricted set of actions
Right now it is possible to pause, suspend and stop a VM in state RESCUED,
so after the state is changed, it's not possible to trigger unrescue anymore
since the original state is lost.
This patch remove vm_states.RESCUED as valid state from stop,
pause and suspend actions.
The vm_states devref is also updated to reflect this change including the
current reboot flow.( vm_states.RESCUED cannot be rebooted as per
today code)
DocImpact
Closes-Bug: #1319182
Co-Authored-By: Cyril Roelandt <email address hidden>
Change-Id: I531dea5a5499bf
Changed in openstack-manuals: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
milestone: | none → juno |
Changed in openstack-manuals: | |
assignee: | nobody → Olga Gusarenko (ogusarenko) |
Changed in openstack-manuals: | |
milestone: | juno → kilo |
status: | In Progress → Confirmed |
Changed in openstack-manuals: | |
milestone: | kilo → liberty |
Changed in openstack-manuals: | |
status: | Confirmed → Fix Released |
Fix proposed to branch: master /review. openstack. org/150385
Review: https:/