Bug 2021607

Summary:	Unable to run openshift-install with a vcenter hostname that begins with a numeric character
Product:	OpenShift Container Platform	Reporter:	Lee McClintock <lmcclint>
Component:	Installer	Assignee:	Aditya Narayanaswamy <anarayan>
Installer sub component:	openshift-installer	QA Contact:	jima
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	anarayan, chdeshpa, mstaeble
Version:	4.8
Target Milestone:	---
Target Release:	4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	If the vcenter hostname begins with a numeric character, the installer validates it as invalid but it is possible to create a vcenter host with a numeric character. Relaxing the validation to allow for numeric characters.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-10 16:26:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2022172

Description Lee McClintock 2021-11-09 18:22:25 UTC

Version:

$ openshift-install version
4.8.0 and up 

Platform:

#Please specify the platform type: aws, libvirt, openstack or baremetal etc.
vsphere 

Please specify:
IPI (automated install with `openshift-install`. If you don't know, then it's IPI)


What happened?

When creating a cluster / manifests with a vcenter hostname that begins with a number, validation fails with the following:

DEBUG       Loading Platform...
FATAL failed to fetch Master Machines: failed to load asset "Install Config": invalid "install-config.yaml" file: platform.vsphere.vCenter: Invalid value: "1your.vcenter.server": must be the domain name or IP address of the vCenter

What did you expect to happen?
cluster / manifests to be created succesfully

How to reproduce it (as minimally and precisely as possible)? Use the sample yaml from the documentation with a vcenter name that begins with a number

/usr/local/bin/openshift-install-4.8.17 create manifests --dir ~/ocp4/vtest --log-level=debug

Anything else we need to know?
This seems to be discussed here: https://github.com/openshift/installer/issues/5126

Comment 1 Matthew Staebler 2021-11-10 14:25:24 UTC

Setting the severity to high as this affects all users trying to install to a vCenter that starts with a number.

Comment 4 jima 2021-11-15 03:52:06 UTC

create install-config.yaml file and set platform.vsphere.vCenter value as "1aaa.bbb.ccc.vmwarevmc.com"

Reproduced the issue on 4.10.0-0.nightly-2021-10-20-193037 with above install-config.yaml file:
$ ./openshift-install version
./openshift-install 4.10.0-0.nightly-2021-10-20-193037
built from commit af4bf5fc2cfe8f1668a3cddeea8ccc2ce070a348
release image registry.ci.openshift.org/ocp/release@sha256:5d55cc3154f38d0bdf92b52b5b14a0b3bb02678abb285bf71e4eefa74d57e1d2
release architecture amd64
$ ./openshift-install create manifests --dir ipi
FATAL failed to fetch Master Machines: failed to load asset "Install Config": invalid "install-config.yaml" file: platform.vsphere.vCenter: Invalid value: "1aaa.bbb.ccc.vmwarevmc.com": must be the domain name or IP address of the vCenter 

Verified on 4.10.0-0.nightly-2021-11-14-184249 with same install-config.yaml file, passed.
$ ./openshift-install version
./openshift-install 4.10.0-0.nightly-2021-11-14-184249
built from commit 8fc863d833b1b361efc61c81998890e1305bcf9b
release image registry.ci.openshift.org/ocp/release@sha256:5e361b1585a5f7ee4eab226853e0b6f707dd52bbfcaee28f53efffddcf118ef9
release architecture amd64
$ ./openshift-install create manifests --dir ipi
FATAL failed to fetch Master Machines: failed to load asset "Install Config": platform.vsphere: Internal error: unable to connect to vCenter 1cc.aaa.bbb.vmwarevmc.com.: Post "https://1cc.aaa.bbb.vmwarevmc.com/sdk": dial tcp: lookup 1cc.aaa.bbb.vmwarevmc.com on xx.xx.xx.xx:53: no such host

Comment 9 errata-xmlrpc 2022-03-10 16:26:15 UTC

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.10.3 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:0056