-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.11.0
-
None
-
Moderate
-
None
-
False
-
Description of problem:
Console pods are stuck in pending state. It seems to happen on small clusters (in my case: 3 workers / 1 master). Message says:
0/4 nodes are available: 1 node(s) didn't match pod anti-affinity rules, 3 node(s) didn't match Pod's node affinity/selector. preemption: 0/4 nodes are available: 1 node(s) didn't match pod anti-affinity rules, 3 Preemption is not helpful for scheduling.
$ oc get pods -n openshift-console NAME READY STATUS RESTARTS AGE console-6f98f898bf-mp44m 1/1 Running 0 3h51m console-76bfb8566-7tzz8 0/1 Pending 0 6m22s console-76bfb8566-p8dpw 0/1 Pending 0 6m22s downloads-755c47f66c-d9t9n 1/1 Running 0 3h51m downloads-755c47f66c-pmtr7 1/1 Running 0 3h52m
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. Spin up a cluster with 3 workers and 1 master 2. Check console pods 3.
Actual results:
2 out of 3 console pods are stuck in pending state (the other has started)
Expected results:
all pods in running state
Additional info:
I didn't see this problem while testing 4.11.0-rc6, so it must be a very recent regression. Also, it seems as a side effect to prevent some dynamic plugins to be properly displayed in the console (NetObserv plugin doesn't show up). I suspect there is a causal relation although I can't be sure.
- is duplicated by
-
-
- Closed
-
