-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
ACM 2.9.0, ACM 2.8.0, ACM 2.7.5
-
False
-
None
-
False
-
-
-
Moderate
-
?
-
No
Description of problem:
If the vSphere datastore in the install-config includes a folder which alters the full/relatve path such as
/Workload Datacenter/datastore/WORKLOAD-DS-Folder/WORKLOAD-DS
or:
WORKLOAD-DS-Folder/WORKLOAD-DS
then OCP 4.12.z deployment will fail. This OCP deployment was done using ACM/Hive.
Note: The relative path (e.g. WORKLOAD-DS) does work. Summary of combinations tried in the table:
Default Datastore | 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 works as expected.
Version-Release number of selected component (if applicable):
2.8.1-DOWNSTREAM-2023-06-15-22-17-59
2.7.5
How reproducible:
always
Steps to Reproduce:
- create a vSphere credential that specifies the full or relative path for the datastore, where a folder is present
- create a vSphere cluster on OCP 4.12.z using ACM
- ...
Actual results:
deployment fails with error
Expected results:
- deploying with either full or relative path should work
Additional info:
- deploying with datastore name only does work for OCP 4.12
- deploying with either full path, relative path or datastore name only works for OCP 4.13
- is blocked by
-
OCPBUGS-22410 Install on vSphere using relative path for datastore is not backwards compatible on OCP 4.13+
- Closed
- is duplicated by
-
ACM-7477 Setting full cluster and datastore paths are required for OCP 4.14
- Closed
- is related to
-
ACM-7477 Setting full cluster and datastore paths are required for OCP 4.14
- Closed
- relates to
-
SPLAT-1093 vSphere: remove legacy platform spec fields
- New