WaitConditions in nested stacks don't work

Bug #1088937 reported by Zane Bitter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Low
Zane Bitter
Grizzly
Fix Released
Low
Zane Bitter

Bug Description

We need to change the RPC API to allow us to report the termination of WaitConditions that are contained in nested stacks. Currently only the top-level stack ID and a resource name are being passed.

Steven Hardy (shardy)
Changed in heat:
assignee: nobody → Steven Hardy (shardy)
milestone: none → grizzly-3
assignee: Steven Hardy (shardy) → nobody
Revision history for this message
Zane Bitter (zaneb) wrote :

Actually, turns out this should work already. I will update the RPC API anyway though, just to make it consistent.

Changed in heat:
importance: High → Low
assignee: nobody → Zane Bitter (zaneb)
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/18419

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/18419
Committed: http://github.com/openstack/heat/commit/f0d3c6e8466d3376cd81fff97efa7e12c6d5b571
Submitter: Jenkins
Branch: master

commit f0d3c6e8466d3376cd81fff97efa7e12c6d5b571
Author: Zane Bitter <email address hidden>
Date: Wed Dec 19 18:48:25 2012 +0100

    RPC API: Pass a stack identifier to metadata_update

    This brings it into line with all of the other RPC functions.

    bug 1088937

    Change-Id: Ia45a12d652e96fb6bb03ce90d0b5a5e2ddeeb510
    Signed-off-by: Zane Bitter <email address hidden>

Changed in heat:
status: In Progress → Fix Committed
Steven Hardy (shardy)
Changed in heat:
milestone: grizzly-3 → grizzly-2
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.