Browse Source

Merge "Default bootstrap_server_id"

changes/02/573102/12
Zuul 4 years ago committed by Gerrit Code Review
parent
commit
46ef074336
  1. 6
      common/deploy-steps.j2
  2. 5
      releasenotes/notes/default-bootstrap-server-id-eff49ef40bfde414.yaml

6
common/deploy-steps.j2

@ -269,7 +269,11 @@ resources:
properties:
value:
yaql:
expression: $.data.items().orderBy($[0]).first()[1]
# Use a constant string of "bootstrap_server_id" when there are no
# servers in the primary role, such as in the case when all
# Controllers are blacklisted. No server id's will match the string
# which is what we want when all are blacklisted.
expression: switch($.data = {} => "no_bootstrap_server", $.data != {} => $.data.items().orderBy($[0]).first()[1])
data: {get_param: [servers, {{primary_role_name}}]}
# Artifacts config and HostPrepConfig is done on all roles, not only

5
releasenotes/notes/default-bootstrap-server-id-eff49ef40bfde414.yaml

@ -0,0 +1,5 @@
---
fixes:
- Previously, when blacklisting all servers of the primary role, the stack
would fail since the bootstrap server id was empty. The value is now
defaulted in case all primary role servers are blacklisted.
Loading…
Cancel
Save