Bug 1882022
| Summary: | [vsphere][ipi] directory path is incomplete, terraform can't find the cluster | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Dan Yocum <dyocum> | ||||
| Component: | Installer | Assignee: | Jeremiah Stuever <jstuever> | ||||
| Installer sub component: | openshift-installer | QA Contact: | jima | ||||
| Status: | CLOSED ERRATA | Docs Contact: | |||||
| Severity: | high | ||||||
| Priority: | high | CC: | adahiya, apurty, jima, jstuever, mabajodu, mstaeble, wking | ||||
| Version: | 4.5 | Keywords: | Reopened | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.7.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2021-02-24 15:19:20 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: | 1918510 | ||||||
| Attachments: |
|
||||||
|
Description
Dan Yocum
2020-09-23 15:45:31 UTC
Per the customer, this is a work-around:
echo "## fixing cloud provider vsphere path" ${_occmd} get cm cloud-provider-config -n openshift-config -o yaml | sed -E "s~folder = \"(.*)\"~folder = \"${_path}\"~g" | ${_occmd} apply -f -
Since it seems like you are using create install-config and then create cluster. Can you please attach 1. the install-config.yaml , feel free to remove the senstive bits like passwords and secrets 2. also the .openshift_install.log 4.5 install issues should not block 4.6 going GA. Punting to 4.7, and any fixes may be backported to 4.5. Created attachment 1718485 [details]
American Systems wrapper scripts for vSphere UPI install
install-config.yaml is located at artifacts/upi-int-install-config.yaml in the tarball.
*** Bug 1890501 has been marked as a duplicate of this bug. *** I have created a JIRA to track this RFE: https://issues.redhat.com/browse/CORS-1586 An JIRA has been created to track this as an RFE. A workaround was discussed in Comment 1. An alternative workaround is to use root folders instead of other locations until this RFE is completed. Closing this BZ in favor of the JIRA. This is a bug. "IE: the installer seeds terraform the path of '/core/host/tims-esp' when the actual path is '/core/host/ResourcePools/tims-esp'" Re-opening to ease tracking in the customer portal. I was able to successfully deploy a cluster where the datacenter is in a folder... (Vcenter/foo/Datacenter-1). The PR for this BZ will include an update to the installer to include the folder name the datacenter value when a user selects one from the prompt which requires it. As a workaround, a user can edit the install-config.yaml and update the datacenter field to include the folder name. For example:
platform:
vsphere:
datacenter: foo/Datacenter-1
I was able to successfully deploy a cluster where the vsphere cluster is in a folder... (Vcenter/Datacenter-1/bar/Cluster-1). The PR for this BZ will include an update to the installer to include the folder name in the cluster value when a user selects one from the prompt which requires it. As a workaround, a user can edit the install-config.yaml and update the cluster field to include the folder name. For example:
platform:
vsphere:
cluster: bar/Cluster-1
Verified on 4.7.0-0.nightly-2021-01-17-211555 by using Jeremiah's vsphere platform and passed.
both cluster and datacenter are in customized folder:
cluster: bar/Cluster-1
datacenter: foo/SDDC-Datacenter
Creating cluster by running "./openshift-install create cluster --dir ipi", and cluster is installed completely.
$ ./oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.7.0-0.nightly-2021-01-18-214951 True False 18m Cluster version is 4.7.0-0.nightly-2021-01-18-214951
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.7.0 security, bug fix, and enhancement 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-2020:5633 |