I0804 01:22:21.534445 1 factory.go:462] Unable to schedule e2e-provisioning-9050/pod-subpath-test-inlinevolume-b9ts: no fit: 0/6 nodes are available: 5 node(s) didn't match node selector.; waiting
I0804 01:22:21.552115 1 factory.go:462] Unable to schedule e2e-provisioning-9050/pod-subpath-test-inlinevolume-b9ts: no fit: 0/6 nodes are available: 5 node(s) didn't match node selector.; waiting
6 nodes but only 5 reasons reported
Upstream fix: https://github.com/kubernetes/kubernetes/pull/93355
The upstream fix is not yet in openshift/kubernetes:release-4.6 branch which is currently rebased to 1.19 rc2.
It is part of 1.19 rc3. Waiting for the next rebase until it gets to 4.6. Once done, we can clone this to 4.5 and fix it there.
4.5 PR https://github.com/openshift/origin/pull/25407
Rama, no need to test this issue. It's mainly for backporting master fix to 4.5 so we can further debug flaking/failing e2e tests.
Checked log from : https://search.ci.openshift.org/?search=Unable+to+schedule&maxAge=48h&context=1&type=junit&name=&maxMatches=5&maxBytes=20971520&groupBy=job.
Can't reproduce the issue now. Will move to verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (OpenShift Container Platform 4.5.8 bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.