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
This commit is contained in:
parent
ce34efda2f
commit
b1ae63bb11
@ -12,6 +12,7 @@ resources:
|
|||||||
BootstrapNodeConfigImpl:
|
BootstrapNodeConfigImpl:
|
||||||
type: OS::Heat::StructuredConfig
|
type: OS::Heat::StructuredConfig
|
||||||
properties:
|
properties:
|
||||||
|
group: os-apply-config
|
||||||
config:
|
config:
|
||||||
bootstrap_host:
|
bootstrap_host:
|
||||||
bootstrap_nodeid: {get_param: bootstrap_nodeid}
|
bootstrap_nodeid: {get_param: bootstrap_nodeid}
|
||||||
|
@ -810,7 +810,6 @@ resources:
|
|||||||
properties:
|
properties:
|
||||||
config: {get_attr: [ControllerBootstrapNodeConfig, config_id]}
|
config: {get_attr: [ControllerBootstrapNodeConfig, config_id]}
|
||||||
servers: {get_attr: [Controller, attributes, nova_server_resource]}
|
servers: {get_attr: [Controller, attributes, nova_server_resource]}
|
||||||
signal_transport: NO_SIGNAL
|
|
||||||
|
|
||||||
ControllerSwiftDeployment:
|
ControllerSwiftDeployment:
|
||||||
type: OS::Heat::StructuredDeployments
|
type: OS::Heat::StructuredDeployments
|
||||||
|
@ -12,6 +12,7 @@ resources:
|
|||||||
BootstrapNodeConfigImpl:
|
BootstrapNodeConfigImpl:
|
||||||
type: OS::Heat::StructuredConfig
|
type: OS::Heat::StructuredConfig
|
||||||
properties:
|
properties:
|
||||||
|
group: os-apply-config
|
||||||
config:
|
config:
|
||||||
hiera:
|
hiera:
|
||||||
datafiles:
|
datafiles:
|
||||||
|
Loading…
Reference in New Issue
Block a user