aboutsummaryrefslogtreecommitdiffstats
path: root/bootstrap-config.yaml
diff options
context:
space:
mode:
authorSteven Hardy <shardy@redhat.com>2015-05-14 07:05:34 -0400
committerGiulio Fidente <gfidente@redhat.com>2015-06-03 16:30:53 +0200
commitb1ae63bb11ce92a584d5dbff4e3dc94564f5cb04 (patch)
treebe88492468d06ac87a35554e52520487bec07c42 /bootstrap-config.yaml
parentce34efda2fa11dd4dc5f46877fd78a784b1b5f56 (diff)
Remove NO_SIGNAL from ControllerBootstrapNodeDeployment
We need to be sure the boostrap node data has been propagated to the cluster before proceeding with configuration, because ControllerNodesPostDeployment consumes the data put in place by this and depends_on for serialization, which is essentially meaningless when combined with NO_SIGNAL. Change-Id: I73a1e5a2cda4c79f457bfbd9ce2836dc5c1902cc
Diffstat (limited to 'bootstrap-config.yaml')
-rw-r--r--bootstrap-config.yaml1
1 files changed, 1 insertions, 0 deletions
diff --git a/bootstrap-config.yaml b/bootstrap-config.yaml
index 6082dbc..c87670e 100644
--- a/bootstrap-config.yaml
+++ b/bootstrap-config.yaml
@@ -12,6 +12,7 @@ resources:
BootstrapNodeConfigImpl:
type: OS::Heat::StructuredConfig
properties:
+ group: os-apply-config
config:
bootstrap_host:
bootstrap_nodeid: {get_param: bootstrap_nodeid}