Stack status IN_PROCESS will not change when restart heat service
Bug #1382320 reported by
Ethan Lynn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Ethan Lynn |
Bug Description
Restart heat services during stack creation.
Then the status of this stack will remain in CREATE_IN_PROCESS, can't automatically change to FAIL or something.
Status IN_PROCESS will confuse customer and they think this stack is still ongoing, but actually it's stopped.
I think it's better change IN_PROCESS to FAIL when restart heat service.
Workaround:
When heat services is restarted, check stack status. If status is IN_PROCESS then change to FAILED.
Need some feedback and then I will work on it.
Changed in heat: | |
assignee: | nobody → Ethan Lynn (ethanlynn) |
Changed in heat: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in heat: | |
milestone: | none → kilo-rc1 |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | kilo-rc1 → 2015.1.0 |
To post a comment you must log in.
I suppose, that you suggestion is good, but may be convergence will solve this problem better or not?