-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.13
-
No
-
Rejected
-
False
-
Description of problem:
After adding the credentials on day 2, I was able to create StorageClass, PersistentVolumeClaim and PersistentVolume but the storage operator is still in the progressing state.
Version-Release number of selected component (if applicable):
4.13
How reproducible:
Always
Steps to Reproduce:
1. Create agent.iso and boot it on vSphere vm. 2. Execute openshift-install agent wait-for install-complete --log-level debug 3. Follow https://access.redhat.com/solutions/6677901 instructions to change the credentials on day 2
Actual results:
Storage operator is in the progressing state as below. storage 4.13.0-0.nightly-2023-03-29-235439 True True False 129m VSphereCSIDriverOperatorCRProgressing: VMwareVSphereDriverNodeServiceControllerProgressing: Waiting for DaemonSet to deploy node pods Also, the `infrastructures.config.openshift.io` is not updated with information provided on day 2. oc get infrastructures.config.openshift.io -o yaml platformSpec: type: VSphere vsphere: failureDomains: - name: generated-failure-domain region: generated-region server: vcenterplaceholder topology: computeCluster: /datacenterplaceholder/host/clusterplaceholder datacenter: datacenterplaceholder datastore: /datacenterplaceholder/datastore/defaultdatastoreplaceholder networks: - networkplaceholder resourcePool: /datacenterplaceholder/host/clusterplaceholder//Resources zone: generated-zone vcenters: - datacenters: - datacenterplaceholder port: 443 server: vcenterplaceholder
Expected results:
Storage operator should be available and not in the progressing status.
Additional info:
The credential instructions provided for day 2 are working fine with 4.12 version.
- is related to
-
OCPBUGS-7563 vSphere install can't complete with out-of-tree CCM
- Closed