Description of problem:
Creating a new machineset with long names was preventing proper DNS resolution of the worker node. All nodes are in Provisioning state forever until manually approve CSR`s.
Cluster working but machines in a not correct stage and the provisioning process needs manual intervention, when it shouldn't
Cluster with all machines in Running stage if everything worked as planned and no manual intervention in the scaling process
Version-Release number of selected component (if applicable):
Deploy a new machineset with long name.
Example of master hostname: openshift-stage-wz4zh-master-0 (30 characters)
Example of infra hostname: openshift-stage-wz4zh-infra-0-j6jsw (35 characters)
Example of worker hostname: openshift-stage-wz4zh-worker-0-tprn9 (36 characters)
Also, looks like this is also affecting the installer, similar issue happened with openstack folks regarding cluster name:
From https://github.com/openshift/installer/issues/2243 we see a long name too:
time="2019-08-19T06:08:55Z" level=info msg="Zeroconf setting service ttl" name="preserve-wjosp0819fa Workstation-preserve-wjosp0819fa-9z8qw-master-0" ttl=3200
time="2019-08-19T06:08:55Z" level=info msg="Zeroconf registering service" name="preserve-wjosp0819fa Etcd-preserve-wjosp0819fa-9z8qw-master-0"
time="2019-08-19T06:08:55Z" level=info msg="Zeroconf registering service" name="preserve-wjosp0819fa Workstation-preserve-wjosp0819fa-9z8qw-master-0"
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.