-
Bug
-
Resolution: Done
-
Major
-
None
-
4.14
-
Important
-
None
-
OCP Node Sprint 269 (Blue), OCP Node Sprint 270 (Blue)
-
2
-
False
-
-
Customer Escalated
Description of problem:
The pods in the openshift-machine-config-operator project are stuck in the Init:0/1 state ~~~ [root@MUM-BO-S3181 ~]# oc get pods -o wide | egrep -v "Running|Completed" NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES kube-rbac-proxy-crio-mum-bo-s3160.klimum.com 0/1 Init:0/1 0 13m 10.3.252.222 mum-bo-s3160.klimum.com <none> <none> kube-rbac-proxy-crio-mum-bo-s3172.klimum.com 0/1 Init:0/1 0 13m 10.3.252.68 mum-bo-s3172.klimum.com <none> <none> kube-rbac-proxy-crio-mum-bo-s3316.klimum.com 0/1 Init:0/1 0 13m 10.3.252.86 mum-bo-s3316.klimum.com <none> <none> ~~~ Even after a restart, issue is the same. No errors are observed in the pod logs, in project events and on nodes.
Version-Release number of selected component (if applicable):
Actual results:
The pods remain stuck in the Init:0/1 state, with no errors or logs indicating the cause of the issue.
Expected results:
The pods should transition from the Init:0/1 state to Running without being stuck, allowing the openshift-machine-config-operator to function as expected.
Additional info:
Logs/Events: - No errors in the pod logs. - No events or unusual entries in project events. - Inspection logs do not provide any additional information about the root cause. Steps Taken to Resolve: - Restarting the pods does not resolve the issue. - Master node reboot didn't help.
- links to