From c270cf0c5ef79869aa5506a789068e5c9565a9b7 Mon Sep 17 00:00:00 2001
From: Alexis Lee <alexisl@hp.com>
Date: Mon, 13 Oct 2014 13:50:54 +0100
Subject: [PATCH] Add block completion signal

In I973d197245ed32612bde9209479e6ae3a443fc69, the signal_transport was
set to NO_SIGNAL to prevent the resource staying CREATE_IN_PROGRESS
forever. This means that Heat reports the stack is configured before it
actually is.

The correct fix was to add completion-signal to BlockStorageConfig.
However now there's a BlockStorage0AllNodesDeployment, we simply have to
receive the signal from allNodesConfig by setting the deployment
signal-transport.

Change-Id: I1f6408ca39fddd146e7aae140f61d265bbf563ec
---
 block-storage.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/block-storage.yaml b/block-storage.yaml
index ae0d6543..172944aa 100644
--- a/block-storage.yaml
+++ b/block-storage.yaml
@@ -27,6 +27,7 @@ resources:
     depends_on: [BlockStorage0Deployment,BlockStorage0PassthroughSpecific]
     type: OS::Heat::StructuredDeployment
     properties:
+      signal_transport: {get_param: DefaultSignalTransport}
       config: {get_resource: allNodesConfig}
       server: {get_resource: BlockStorage0}
   BlockStorage0Deployment:
-- 
2.16.6