LoadBalancer resource doesn't delete nested stack

Bug #1097394 reported by Steven Hardy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
High
Steven Hardy
Grizzly
Fix Released
High
Steven Hardy

Bug Description

Similar to DBInstance issue ref bug 1097299, when a stack containing an AWS::ElasticLoadBalancing::LoadBalancer resource is deleted, the underlying nested stack (and related instance, and DB contents) is not deleted.

The reason is the resource inherits from stack.Stack not stack.NestedStack, and stack.Stack doesn't implement handle_delete()

Steven Hardy (shardy)
Changed in heat:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Steven Hardy (shardy)
milestone: none → grizzly-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to heat (master)

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

Changed in heat:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to heat (master)

Reviewed: https://review.openstack.org/19226
Committed: http://github.com/openstack/heat/commit/c975a0e005612133a8188fa7490f6c3ff1899027
Submitter: Jenkins
Branch: master

commit c975a0e005612133a8188fa7490f6c3ff1899027
Author: Steven Hardy <email address hidden>
Date: Tue Jan 8 18:47:05 2013 +0000

    heat engine : LoadBalancer resource delete nested stack

    Ensure LoadBalancer resource deletes the underlying nested
    stack when the owning stack is deleted - needs to inherit
    from stack.NestedStack as this implements handle_delete()

    fixes bug 1097394

    Change-Id: I2002bed361511a495cbdf38cad7b61e148a68ba2
    Signed-off-by: Steven Hardy <email address hidden>

Changed in heat:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in heat:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: grizzly-2 → 2013.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.