diff options
author | OpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com> | 2018-02-08 15:08:03 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2018-02-08 15:08:03 -0800 |
commit | 70914a6b13d9462e5348af268a67691c641d6634 (patch) | |
tree | 69a1118e1f8ebdc832359efa58a0ea028db41732 /test/ci | |
parent | 26a72e6bb86d8c85c41c269bf1bd4dd8f3a5cd15 (diff) | |
parent | 16ae2ef84266dfdb1b9af493704579aeebc7284f (diff) | |
download | openshift-70914a6b13d9462e5348af268a67691c641d6634.tar.gz openshift-70914a6b13d9462e5348af268a67691c641d6634.tar.bz2 openshift-70914a6b13d9462e5348af268a67691c641d6634.tar.xz openshift-70914a6b13d9462e5348af268a67691c641d6634.zip |
Merge pull request #7061 from gnewson/Change-etcd-check
Automatic merge from submit-queue.
Changing the check for the number of etcd nodes
This playbook is called (via std_include.yml) when the scale up playbook for either master or etcd is called. In the scenario where you are scaling up the number of masters/etcd nodes it is feasible, if not likely, that the number of etcd nodes is not 1, 3 or 5 and this check therefore causes a scale up to fail.
The two example scenarios that are driving this change are:
You have a cluster with 3 master nodes (each running etcd) and one of those masters fail. The master node is removed from both the OpenShift cluster and the etcd cluster and the inventory updated to reflect the state of the cluster minus the failed master node. You would then run the scale up playbook to add a new master / etcd master into the cluster using an inventory containing and etcd group of just 2 nodes.
As above but the cluster has 5 master nodes. If you lose a master node and update the inventory to reflect that then the inventory will contain an etcd group with 4 nodes.
@sdodson
Previously submitted as https://github.com/openshift/openshift-ansible/pull/6979
Diffstat (limited to 'test/ci')
0 files changed, 0 insertions, 0 deletions