ResourceGroup removal_policies not applied on create

Bug #1585206 reported by Zane Bitter on 2016-05-24
14
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.

Fix proposed to branch: master
Review: https://review.openstack.org/320456

Changed in heat:
status: Triaged → In Progress
Rabi Mishra (rabi) on 2016-06-01
Changed in heat:
milestone: newton-1 → newton-2
Thomas Herve (therve) on 2016-07-12
Changed in heat:
milestone: newton-2 → newton-3

Reviewed: https://review.openstack.org/320456
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=5f1d3bb6d666bbd7ad75b7852285eec297af8593
Submitter: Jenkins
Branch: master

commit 5f1d3bb6d666bbd7ad75b7852285eec297af8593
Author: Zane Bitter <email address hidden>
Date: Tue May 24 09:29:48 2016 -0400

    Apply ResourceGroup blacklist at create time

    Because of the requirement that the nested stack exist, the blacklist was
    previously ignored at the time the ResourceGroup was created and only
    applied on subsequent updates.

    Change-Id: I43dbb13e12fad349a226cffe5d0e96ed7fce3aeb
    Closes-Bug: #1585206

Changed in heat:
status: In Progress → Fix Released

This issue was fixed in the openstack/heat 7.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers