Bug 2076393

Summary:	[VSphere] survey fails to list datacenters
Product:	OpenShift Container Platform	Reporter:	Jeremiah Stuever <jstuever>
Component:	Installer	Assignee:	Jeremiah Stuever <jstuever>
Installer sub component:	openshift-installer	QA Contact:	jima
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	urgent	CC:	jima
Version:	4.11
Target Milestone:	---
Target Release:	4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-10 11:07:40 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:

Description Jeremiah Stuever 2022-04-18 22:14:08 UTC

Version:

$ openshift-install version
openshift-install unreleased-master-5893-gb3397f02321e70e717f2245e5c424908aad5d21c
built from commit b3397f02321e70e717f2245e5c424908aad5d21c
release image registry.ci.openshift.org/origin/release:4.11
release architecture amd64


Platform:

vsphere

Please specify:

IPI

What happened?

Received the following error after completing password survey prompt.

INFO Connecting to vcenter
FATAL failed to fetch Install Config: failed to fetch dependency of "Install Config": failed to fetch dependency of "Base Domain": failed to generate asset "Platform": unable to list datacenters: datacenter '/...' not found 

What did you expect to happen?

Survey should have prompted for datacenters or selected one by default.

How to reproduce it (as minimally and precisely as possible)?

$ rm -rf assets
$ openshift-install --dir=assets create install-config
? Platform vsphere

Anything else we need to know?

Comment 8 jima 2022-04-24 02:07:54 UTC

Reproduced the issue on 4.11.0-0.nightly-2022-04-21-025500

$ ./openshift-install create cluster --dir ipi
? SSH Public Key /home/jima/.ssh/openshift-qe.pub
? Platform vsphere
? vCenter xxxxxx
? Username xxxxxx
? Password [? for help] **************
INFO Connecting to vCenter vcenter.sddc-44-236-21-251.vmwarevmc.com
FATAL failed to fetch Metadata: failed to fetch dependency of "Metadata": failed to fetch dependency of "Cluster ID": failed to fetch dependency of "Install Config": failed to fetch dependency of "Base Domain": failed to generate asset "Platform": unable to list datacenters: datacenter '/...' not found

Verified on 4.11.0-0.nightly-2022-04-22-233137 and passed.
$ ./openshift-install create cluster --dir ipi
? SSH Public Key /home/jima/.ssh/openshift-qe.pub
? Platform vsphere
? vCenter xxxxxx
? Username xxxxxx
? Password [? for help] **************
INFO Connecting to xxxxxx
INFO Defaulting to only available datacenter: SDDC-Datacenter
INFO Defaulting to only available cluster: Cluster-1
? Default Datastore WorkloadDatastore
? Network qe-segment
? Virtual IP Address for API xxx.xxx.xxx.xxx
? Virtual IP Address for Ingress xxx.xxx.xxx.xxx
? Base Domain qe.devcluster.openshift.com
? Cluster Name jima0424
? Pull Secret [? for help] ***********************************
INFO Obtaining RHCOS image file from 'https://rhcos-redirector.apps.art.xq1c.p1.openshiftapps.com/art/storage/releases/rhcos-4.11/411.85.202203181601-0/x86_64/rhcos-411.85.202203181601-0-vmware.x86_64.ova?sha256='
INFO The file was found in cache: /home/jima/.cache/openshift-installer/image_cache/rhcos-411.85.202203181601-0-vmware.x86_64.ova. Reusing...
INFO Creating infrastructure resources...
INFO Waiting up to 20m0s (until 2:23AM) for the Kubernetes API at https://api.jima0424.qe.devcluster.openshift.com:6443...
INFO API v1.23.3+d464c70 up
INFO Waiting up to 30m0s (until 2:36AM) for bootstrapping to complete...

Comment 10 errata-xmlrpc 2022-08-10 11:07:40 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 (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.

https://access.redhat.com/errata/RHSA-2022:5069