-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.14
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
After shutting the cluster for some months, CX cluster is unable to startup or pods are stuck in Pending state due to insufficient memory: kube-scheduler: 2024-11-22T10:59:38.725865474Z I1122 10:59:38.725851 1 schedule_one.go:889] "Unable to schedule pod; no fit; waiting" pod="openshift-operator-lifecycle-manager/collect-profiles-28852815-fnkkm" err="0/1 nodes are available: 1 Insufficient memory. preemption: Internal error occurred: failed calling webhook \"pod.network-node-identity.openshift.io\": failed to call webhook: Post \"https://127.0.0.1:9743/pod?timeout=10s\": dial tcp 127.0.0.1:9743: connect: connection refused." However it appears that there is a lot of memory available on the node.
Version-Release number of selected component (if applicable):
4.14
How reproducible:
consistently
Steps to Reproduce:
1. 2. 3.
Actual results:
Pods unable to schedule on single node cluster
Expected results:
Pods should be able to schedule correctly
Additional info: