disable_rollback will change to true although we don't specify it when stack-update
Bug #1324366 reported by
Ethan Lynn
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Pavlo Shchelokovskyy | ||
python-heatclient |
Fix Released
|
Medium
|
Pavlo Shchelokovskyy |
Bug Description
Steps:
heat stack-create -f aa.template -P flavor=m1.tiny --enable-rollback
heat stack-update -f aa.template -P flavor=m1.small
Result:
When update action is failed, no rollback action is going.
Since this patch (https:/
no rollback action will take after update failed.
I think disable_rollback should inherit from oldstack if we don't specify it when stack-update.
Or add option --enable-rollback to stack-update cli.
description: | updated |
description: | updated |
Changed in python-heatclient: | |
assignee: | Pavlo Shchelokovskyy (pshchelo) → Zhang Yang (neil-zhangyang) |
status: | New → In Progress |
Changed in heat: | |
importance: | Undecided → Medium |
milestone: | none → juno-rc1 |
Changed in python-heatclient: | |
importance: | Undecided → Medium |
milestone: | none → v0.2.11 |
Changed in python-heatclient: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | juno-rc1 → 2014.2 |
To post a comment you must log in.
There is a patch for cli and pending to review. /review. openstack. org/#/c/ 94004
https:/