Bug 1955697
Summary: | [vsphere] If there are multiple datacenters with the same name installation fails | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jeremiah Stuever <jstuever> |
Component: | Installer | Assignee: | OCP Installer <ocp-installer> |
Installer sub component: | openshift-installer | QA Contact: | jima |
Status: | CLOSED DEFERRED | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | bleanhar, jcallen, jima, morgan.peterman, nstielau, padillon |
Version: | 4.8 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1918005 | Environment: | |
Last Closed: | 2023-03-09 01:28:22 UTC | Type: | --- |
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: | 1981941 | ||
Bug Blocks: |
Comment 2
jima
2021-05-20 02:36:03 UTC
If I recall, we paused on this bug because there isn't currently a combination that works for this value between the vsphere-private Terraform provider and the in-cluster cloud controller. We were discussing upgrading the community Terraform VSphere provider to a newer version which will obsolete the vsphere-private code. However, that change is blocked by the work to split terraform templates into stages to enable us to upgrade to newer versions. https://issues.redhat.com/browse/CORS-1696 Waiting on terraform upgrade. After terraform upgraded (https://issues.redhat.com/browse/CORS-1696), issue still exist when multiple datacenters with the same name. tested on 4.11.0-0.nightly-2022-06-21-151125 $ ./openshift-install create cluster --dir ipi-dc ? SSH Public Key /home/jima/.ssh/ssh.pub ? Platform vsphere ? vCenter xxxxxx ? Username openshift-qe ? Password [? for help] ********** INFO Connecting to vCenter xxxxxx INFO Defaulting to only available datacenter: Datacenter ? Cluster jima/reliability ? Default Datastore datastore3 ? Network VM Network ? Virtual IP Address for API 10.8.33.103 ? Virtual IP Address for Ingress 10.8.33.104 ? Base Domain qe.devcluster.openshift.com ? Cluster Name jima23a ? Pull Secret [? for help] **************** ERROR ERROR Error: error fetching datacenter: path 'Datacenter' resolves to multiple datacenters ERROR ERROR with data.vsphere_datacenter.datacenter, ERROR on main.tf line 20, in data "vsphere_datacenter" "datacenter": ERROR 20: data "vsphere_datacenter" "datacenter" { ERROR ERROR failed to fetch Cluster: failed to generate asset "Cluster": failure applying terraform for "pre-bootstrap" stage: failed to create cluster: failed to apply Terraform: exit status 1 ERROR ERROR Error: error fetching datacenter: path 'Datacenter' resolves to multiple datacenters ERROR ERROR with data.vsphere_datacenter.datacenter, ERROR on main.tf line 20, in data "vsphere_datacenter" "datacenter": ERROR 20: data "vsphere_datacenter" "datacenter" { ERROR ERROR OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira. https://issues.redhat.com/browse/OCPBUGS-9699 |