-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.16
-
Moderate
-
None
-
OpenShift SPLAT - Sprint 261, OpenShift SPLAT - Sprint 262, OpenShift SPLAT - Sprint 263
-
3
-
False
-
Description of problem:
Customer is able to deploy using OCP4.14, but not OCP 4.16.8 on the same cluster
Version-Release number of selected component (if applicable):
vCenter: 8.0.2 23319993 ESXi: 8.0.2 23305546 DRS: Migration automation level: Fully Automated Migration threshold: Apply only priority 1 recommendations. Power management automation level: Off Scalable shares: All resource pools' shares are scalable
How reproducible:
always
Steps to Reproduce:
1. (Using ACM,) openshift-install 4.16 create cluster using user provide YaML Manifest
Actual results:
error
Expected results:
cluster creation
Additional info:
This potential bug seems not related to OCPBUGS-38559, nor OCPBUGS-37945, nor OCPBUGS-38560.
Here the customer finds out relevant information regarding disk file path
fail log :
--> vmPathName = "ds:///vmfs/volumes/65d5f1f7-aa9917f1-f801-7657c0b00002/",
[...]
--> fileName = "ds:///vmfs/volumes/65d5f1f7-aa9917f1-f801-7657c0b00002/",
success log :
--> vmPathName = "ds:///vmfs/volumes/625ec158-146434d8-3e4c-42eeaaf0005a/coreos/coreos.vmx",
[...]
--> fileName = "ds:///vmfs/volumes/625ec158-146434d8-3e4c-42eeaaf0005a/coreos/coreos.vmdk",