Hide Forgot
Version: OCP 4.9 Platform: oVirt * IPI What happened? User reports that they are not able to create OCP cluster in RHV IPI where the name of the cluster is > 14 characters: ~~~ Sorry, your answer is not valid: it must not be more than 14 characters". cluster name "<morethan14charactername>" ~~~ Looking at https://github.com/openshift/installer/blob/master/pkg/asset/installconfig/clustername.go#L45-L50 I see there's a note stating that this limitation should be removed once BZ 1915122 gets fixed. BZ 1915122 got fixed already and shipped to OCP 4.8 and 4.7 (1983695), thus we would need to remove this limitation for users to be able to create clusters with a name > than 14 characters.
@pelauter can you please advise on the priority and severity of this issue? Do we want to implement it, or close as WONTFIX?
In the context of https://bugzilla.redhat.com/show_bug.cgi?id=1915122 a limitation in the mdns-publisher was introduced that caps the length of a cluster name to 63 chars (by hashing longer names): https://github.com/openshift/mdns-publisher/pull/24 Therefore, instead of removing the cluster name length completely, we'll increase it from 14 to 63 chars.
Verified on - 4.12.0-0.nightly-2022-09-02-194931 I have used a medatada cluster name called 'longclustername123'(18 characters) https://api.longclustername123.ocp.rhev.x.x.x.x.x:6443/version INFO API v1.24.0+a097e26 up INFO Install complete! INFO Access the OpenShift web-console here: https://console-openshift-console.apps.longclustername123.ocp.rhev.x.x.x.x oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.12.0-0.nightly-2022-09-02-194931 True False 92s Cluster version is 4.12.0-0.nightly-2022-09-02-194931 The 14 characters limitation is gone now and cluster is installed successfully.
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.12.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. https://access.redhat.com/errata/RHSA-2022:7399