Resize instance via Heat might fail
Bug #1471135 reported by
Bruno Bompastor
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Kairat Kushaev | ||
Kilo |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Changing the flavor of the instance on a heat template and then issuing a stack-update might fail.
This happens here: https:/
When a server says ACTIVE, than heat does a resize, and by the time check_resize is executed for the first time, server status is still ACTIVE - heat will through error.
The proposed fix is to verify that resize is only allowed for ACTIVE states, and then add ACTIVE as allowed value in check_resize.
I tested this on Juno but since the code has not changed in master the bug is still there.
Changed in heat: | |
assignee: | nobody → Kairat Kushaev (kkushaev) |
Changed in heat: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in heat: | |
status: | Triaged → In Progress |
Changed in heat: | |
status: | In Progress → Fix Committed |
tags: | added: kilo-backport-potential |
Changed in heat: | |
milestone: | none → liberty-2 |
status: | Fix Committed → Fix Released |
tags: | removed: kilo-backport-potential |
Changed in heat: | |
milestone: | liberty-2 → 5.0.0 |
tags: | removed: in-stable-kilo |
To post a comment you must log in.
Is it possible to backport this to Juno?