Make Wait Conditions depend on config creation
authorClint Byrum <clint@fewbar.com>
Wed, 26 Feb 2014 22:27:24 +0000 (14:27 -0800)
committerClint Byrum <clint@fewbar.com>
Wed, 26 Feb 2014 22:27:24 +0000 (14:27 -0800)
Currently our wait conditions are racing with Heat resolving
configurations. There should be plenty of time but sometimes Heat may
be dealing with a temporarily problematic Nova API and spinning on that.
While that is happening, the in-instance tools will not have their full
configuration available to them. We don't want the wait condition timeout
to start until the box has had its actual config exposed to it.

Change-Id: I0eab8fe7547d3cbcebb1559fd3d06206b1750e96

nova-compute-instance.yaml
overcloud-source.yaml

index 55665dc..13cc231 100644 (file)
@@ -108,7 +108,7 @@ Resources:
         Ref: ComputeUser
   NovaCompute0CompletionCondition:
     Type: AWS::CloudFormation::WaitCondition
-    DependsOn: notCompute0
+    DependsOn: notCompute0Config
     Properties:
       Handle: {Ref: NovaCompute0CompletionHandle}
       Count: '1'
index 6d21a4d..83844f2 100644 (file)
@@ -144,7 +144,7 @@ Resources:
     Type: AWS::IAM::AccessKey
   notCompute0CompletionCondition:
     Type: AWS::CloudFormation::WaitCondition
-    DependsOn: notCompute0
+    DependsOn: notCompute0Config
     Properties:
       Handle: {Ref: notCompute0CompletionHandle}
       Count: '1'