9cde9139c4
This solves the problem that bootstrap_nodeid, which is set to the first node in each role via t-h-t, can match potentially more than one node - e.g in the event that a service is deployed such that it spans more than one role. The SERVICE_short_bootstrap_node_name is automatically generated based on the composable service template service_name, and this considers all roles where the service is enabled, e.g it should only evaluate true once regardles off the roles where the service is enabled. Change-Id: I48ec4549552910f3cb8db960b0ff10a6c61b4bb9 Partial-Bug: #1792613
9 lines
397 B
YAML
9 lines
397 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
All manifests no longer use the bootstrap_nodeid hiera key, since this
|
|
was generated per role and can result in multiple bootstrap nodes when
|
|
a service on more than one role. The SERVICE_short_bootstrap_node_name
|
|
key is used instead, which is automatically generated in tripleo-heat-templates
|
|
based on the service_name key of the service template role_data.
|