Description of problem: When OCP installer creates master nodes, they are numbered from 0 onwards. Example (six is name of my OCP cluster): six-rz59f-master-0 six-rz59f-master-1 six-rz59f-master-2 However, worker nodes created by the installer have all number 0 suffixed: six-rz59f-worker-0-4tvgb six-rz59f-worker-0-mcjx7 I understand this is because of the Machine Set whose name is "six-rz59f-worker-0" and the individual worker nodes are just variations of this Machine Set's name. However, it would be better if we could achieve the same sequential numbering that we have with masters. And if not, then I suggest to remove number 0 from the default worker Machine Set altogether, because that number does not give any valuable information and is only confusing since it *looks like* the nodes are supposed to be ordered, but actually they aren't. Version-Release number of the following components: openshift-install-linux-4.4.0-0.nightly-2020-03-26-041820 How reproducible: 100 % Steps to Reproduce: 1. Run openshift-install Actual results: ./oc get no NAME STATUS ROLES AGE VERSION six-rz59f-master-0 Ready master 20h v1.17.1 six-rz59f-master-1 Ready master 20h v1.17.1 six-rz59f-master-2 Ready master 20h v1.17.1 six-rz59f-worker-0-4tvgb Ready worker 20h v1.17.1 six-rz59f-worker-0-mcjx7 Ready worker 20h v1.17.1 Expected results: Worker nodes should either be numbered sequentially or the number should be removed from Machine Set name
due to capacity constraints we will be revisiting this bug in the upcoming sprint
same as comment #3 and comment #2
*** Bug 1877926 has been marked as a duplicate of this bug. ***
nice to have, low priority. Workers doesn't really need to be numbered.
Fixed: https://github.com/openshift/installer/pull/4723
rhv: 4.4.5.10 ocp: 4.8.0-0.nightly-2021-03-22-104536 look on Workers name and they are without 0 at the end
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438