This is a clone of issue OCPBUGS-22410. The following is the description of the original issue:
—
Description of problem:
Original issue reported here: https://issues.redhat.com/browse/ACM-6189 reported by QE and customer.
Using ACM/hive, customers can deploy Openshift on vSphere. In the upcoming release of ACM 2.9, we support customers on OCP 4.12 - 4.15. ACM UI updates the install config as users add configurations details.
This has worked for several releases over the last few years. However in OCP 4.13+ the format has changed and there is now additional validation to check if the datastore is a full path.
As per https://issues.redhat.com/browse/SPLAT-1093, removal of the legacy fields should not happen until later, so any legacy configurations such as relative paths should still work.
Version-Release number of selected component (if applicable):
ACM 2.9.0-DOWNSTREAM-2023-10-24-01-06-09 OpenShift 4.14.0-rc.7 OpenShift 4.13.18 OpenShift 4.12.39
How reproducible:
Always
Steps to Reproduce:
1. Deploy OCP 4.12 on vSphere using legacy field and relative path without folder (e.g. platform.vsphere.defaultDatastore: WORKLOAD-DS 2. Installer passes. 3. Deploy OCP 4.12 on vSphere using legacy field and relative path WITH folder (e.g. platform.vsphere.defaultDatastore: WORKLOAD-DS-Folder/WORKLOAD-DS 4. Installer fails. 5. Deploy OCP 4.12 on vSphere using legacy field and FULL path (e.g. platform.vsphere.defaultDatastore: /Workload Datacenter/datastore/WORKLOAD-DS-Folder/WORKLOAD-DS 6. Installer fails. 7. Deploy OCP 4.13 on vSphere using legacy field and relative path without folder (e.g. platform.vsphere.defaultDatastore: WORKLOAD-DS 8. Installer fails. 9. Deploy OCP 4.13 on vSphere using legacy field and relative path WITH folder (e.g. platform.vsphere.defaultDatastore: WORKLOAD-DS-Folder/WORKLOAD-DS 10. Installer passes. 11. Deploy OCP 4.13 on vSphere using legacy field and FULL path (e.g. platform.vsphere.defaultDatastore: /Workload Datacenter/datastore/WORKLOAD-DS-Folder/WORKLOAD-DS 12. Installer fails.
Actual results:
| Default Datastore Value | OCP 4.12 | OCP 4.13 | OCP 4.14 |
|---|---|---|---|
| /Workload Datacenter/datastore/WORKLOAD-DS-Folder/WORKLOAD-DS | No | Yes | Yes |
| WORKLOAD-DS-Folder/WORKLOAD-DS | No | Yes | Yes |
| WORKLOAD-DS | Yes | No | No |
For OCP 4.12.z managed clusters deployments name-only path is the only one that works as expected.
For OCP 4.13.z+ managed cluster deployments only full name and relative path with folder works as expected.
Expected results:
OCP 4.13.z+ takes relative path without specifying the folder like OCP 4.12.z does.
Additional info:
- clones
-
OCPBUGS-22410 Install on vSphere using relative path for datastore is not backwards compatible on OCP 4.13+
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
-
RHBA-2024:5751
OpenShift Container Platform 4.15.z bug fix update