$ openshift-install version
built from commit 7edd680768c4d58a72dea0d3f49dbd7cbc1fa03c
release image registry.ci.openshift.org/ocp/release@sha256:e7e44a81f41823198bbfa21129cd00584714c346e7c9355c56e433bfbc52d452
release architecture amd64
Installation fails when the cluster name contains a dot ("."), there is however no check during the installation to notify about having dot in the ".metadata.name" field in install-config.yaml
What did you expect to happen?
Interrupting the installation and notifying about not valid cluster name (assuming there are no dots allowed in cluster name as this causes VRRP issues in keepalived)
How to reproduce it (as minimally and precisely as possible)?
put a dot to ".metadata.name" in install-config
Note,this bug origin from Bug 2084580 - [4.10] No cluster name sanity validation - cluster name with a dot (".") character.
Thanks for raising this; We'll make a bugfix with explicit validation for the character.
This bug has been verified on OCP 4.11.0-0.nightly-2022-06-22-190830 and passed, thanks.
1, when creating install-config with cluster name contains a dot (".")
# ./openshift-install create install-config --dir cluster
? Virtual IP Address for API 10.0.132.20
? Virtual IP Address for Ingress 10.0.132.21
? Base Domain qe.devcluster.openshift.com
X Sorry, your reply was invalid: cluster name must not contain '.'
2, when install-config.yaml with cluster name contains a dot (".")
# ./openshift-install create manifests --dir cluster
ERROR failed to fetch Master Machines: failed to load asset "Install Config": failed to create install config: invalid "install-config.yaml" file: metadata.name: Invalid value: "sgao.test": cluster name must not contain '.'
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 (Important: OpenShift Container Platform 4.11.0 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.