cannot resume a stack after it was action-checked while suspended
Bug #1506042 reported by
Removed by request
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Triaged
|
Medium
|
Unassigned |
Bug Description
A stack cannot resume, since state CHECK_COMPLETE is invalid for resuming.
IMO safest thing here is to disable check on a suspended stack.
Changed in heat: | |
assignee: | nobody → Masco Kaliyamoorthy (masco) |
Changed in heat: | |
assignee: | Masco (masco) → nobody |
status: | In Progress → Confirmed |
Changed in heat: | |
milestone: | mitaka-2 → mitaka-3 |
Changed in heat: | |
milestone: | mitaka-3 → mitaka-rc1 |
Changed in heat: | |
milestone: | mitaka-rc1 → newton-1 |
Changed in heat: | |
assignee: | nobody → Di XiaoLi (dixiaobj) |
Changed in heat: | |
assignee: | Di XiaoLi (dixiaobj) → nobody |
Changed in heat: | |
status: | In Progress → Triaged |
milestone: | newton-1 → next |
Changed in heat: | |
assignee: | nobody → Tanvir Talukder (tanvirt16) |
Changed in heat: | |
status: | Triaged → In Progress |
Changed in heat: | |
assignee: | Tanvir Talukder (tanvirt16) → nobody |
status: | In Progress → Triaged |
To post a comment you must log in.
Amit, I thought about it several times, but looks like it will not do it more safer...
Probably the right solution is to revise events for previous states and if it was suspended before the check or something else (what allowed after suspend) we may do resume.
I am not the fan of the simple disabling such check.