Failure after the update of a suspended stack
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Angus Salkeld | ||
Havana |
Fix Released
|
Medium
|
Unassigned |
Bug Description
How to reproduce:
- Create a stack with OS::Heat:
- Suspend the stack
- Update the stack with instances number = N+1
=> the status of the stack gets UPDATE_FAILED
=> when trying to resume the stack, it fails too as only a SUSPEND_COMPLETE stack can be resumed.
It would probably best to discard stack updates when in SUSPEND_COMPLETE state.
Heat engine logs (after the update):
2013-10-02 17:03:24.690 22867 ERROR heat.engine.
2013-10-02 17:03:24.690 22867 TRACE heat.engine.
2013-10-02 17:03:24.690 22867 TRACE heat.engine.
2013-10-02 17:03:24.690 22867 TRACE heat.engine.
2013-10-02 17:03:24.690 22867 TRACE heat.engine.
2013-10-02 17:03:24.690 22867 TRACE heat.engine.
2013-10-02 17:03:24.690 22867 TRACE heat.engine.
2013-10-02 17:03:24.690 22867 TRACE heat.engine.
2013-10-02 17:03:24.690 22867 TRACE heat.engine.
2013-10-02 17:03:24.690 22867 TRACE heat.engine.
2013-10-02 17:03:24.690 22867 TRACE heat.engine.
2013-10-02 17:03:24.690 22867 TRACE heat.engine.
Changed in heat: | |
assignee: | nobody → Angus Salkeld (asalkeld) |
importance: | Undecided → Medium |
status: | New → Triaged |
milestone: | none → icehouse-1 |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | icehouse-1 → 2014.1 |
I agree, I think the easiest fix is just to not allow stacks to be updated if they're suspended.