-
Bug
-
Resolution: Done-Errata
-
Major
-
4.15
Description of problem:
The degradation of the storage operator occurred because it couldn't locate the node by UUID. I noticed that the providerID was present for node 0, but it was blank for other nodes. A successful installation can be achieved on day 2 by executing step 4 after step 7 from this document: https://access.redhat.com/solutions/6677901. Additionally, if we provide credentials from the install-config, it's necessary to add a taint to the node using the uninitialized taint(oc adm taint node "$NODE" node.cloudprovider.kubernetes.io/uninitialized=true:NoSchedule) after the bootstrap completed.
Version-Release number of selected component (if applicable):
4.15
How reproducible:
100%
Steps to Reproduce:
1. Create an agent ISO image 2. Boot the created ISO on vSphere VM
Actual results:
Installation is failing due to storage operator unable to find the node by UUID.
Expected results:
Storage operator should be installed without any issue.
Additional info:
Slack discussion: https://redhat-internal.slack.com/archives/C02SPBZ4GPR/p1702893456002729
- blocks
-
AGENT-545 Use vSphere credentials from install-config
- Closed
- is cloned by
-
OCPBUGS-29485 vSphere ABI failed due to storage operator degraded
- Closed
-
OCPBUGS-38220 [4.14] vSphere ABI failed due to storage operator degraded
- Closed
- is depended on by
-
OCPBUGS-29485 vSphere ABI failed due to storage operator degraded
- Closed
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update
(2 links to)