diff options
| author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2018-02-14 14:28:33 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-02-14 14:28:33 -0800 |
| commit | b62c397f0625b9ff3654347a1777ed2277942712 (patch) | |
| tree | 950a36359a9ac5e7d4a0b692ccdaf43e6f106463 /playbooks/openstack/openshift-cluster/provision.yml | |
| parent | deb9a793cbb169b964424720f9c3a6ce6b976b09 (diff) | |
| parent | 61df593d2047995f25327e54b32956944f413100 (diff) | |
| download | openshift-b62c397f0625b9ff3654347a1777ed2277942712.tar.gz openshift-b62c397f0625b9ff3654347a1777ed2277942712.tar.bz2 openshift-b62c397f0625b9ff3654347a1777ed2277942712.tar.xz openshift-b62c397f0625b9ff3654347a1777ed2277942712.zip | |
Merge pull request #7097 from ewolinetz/logging_fresh_lg_cluster_fix
Automatic merge from submit-queue.
Whenever we create a new es node ignore health checks, changing prome…
…theus pw gen for increased secret idempotency
Addresses https://bugzilla.redhat.com/show_bug.cgi?id=1540099
Whenever we are in a cluster sized > 1 the nodes required for recovery > 1. So when we have a fresh install we will not see the cluster start up because the number of required nodes is not met.
Whenever we are creating a new node, we do not wait for the health check so that the logging playbook can complete and we can roll out all updated nodes.
Also addresses prometheus pw generation so that each rerun of the playbook doesn't change the secret which triggers a full rollout of the cluster (assumes that keys/certs have changed).
Diffstat (limited to 'playbooks/openstack/openshift-cluster/provision.yml')
0 files changed, 0 insertions, 0 deletions