Description of problem:
After upgrading OCP and LSO to version 4.14, elasticsearch pods in the openshift-logging deployment are unable to schedule to their respective nodes and remain Pending, even though the LSO managed PVs are bound to the PVCs. A test pod using a newly created test PV managed by the LSO is able to schedule correctly however.
Version-Release number of selected component (if applicable):
4.14
How reproducible:
Consistently
Steps to Reproduce:
1.
2.
3.
Actual results:
Pods consuming previously existing LSO managed PVs are unable to schedule and remain in a Pending state after upgrading OCP and LSO to 4.14.
Expected results:
That pods would be able to consume LSO managed PVs and schedule correctly to nodes.
Additional info:
- blocks
-
OCPBUGS-42427 4.17: After upgrading OCP and LSO to 4.14, openshift-logging elasticsearch pods will not bind to PVC and remain in Pending state
-
- Closed
-
- is cloned by
-
-
- Closed
-
- links to
-
RHEA-2024:6121
OpenShift Container Platform 4.18.z extras update
