Rolling update scaledown of ResourceGroup does not replace FAILED Resources
Bug #1517079 reported by
Rabi Mishra
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
New
|
Medium
|
Rabi Mishra |
Bug Description
While scaling down (reducing COUNT) with rolling_update, if there are FAILED resources and the COUNT is less than current valid_resources, the FAILED resources are not replaced, irrespective of their index being lower.
However, when there is scaling up this is replaced as part of fix to bug 1508736.
Changed in heat: | |
importance: | Undecided → Medium |
assignee: | nobody → Rabi Mishra (rabi) |
Changed in heat: | |
milestone: | none → no-priority-tag-bugs |
To post a comment you must log in.
As I remembered, when the stack update fails, user will not be able to update the resources, only can re-create the stack. And could you show more details about your failed sale down and successful scale up?