ResourceGroup removal_policies not applied on create
Bug #1585206 reported by
Zane Bitter
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Zane Bitter |
Bug Description
If resource names in a ResourceGroup are blacklisted by a removal policy at the time the group is created, the policy is ignored. It will be applied on the next update. This leads to inconsistent behaviour, as an update with no changes can delete and replace a resource.
It's also a pain for anyone who wants 1-based indices, and hence wants to blacklist resource 0 from the start.
Changed in heat: | |
milestone: | newton-1 → newton-2 |
Changed in heat: | |
milestone: | newton-2 → newton-3 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/320456
Review: https:/