fail [k8s.io/kubernetes/test/e2e/scheduling/priorities.go:191]: Expected error: <*errors.errorString | 0xc0002ca210>: { s: "timed out waiting for the condition", } timed out waiting for the condition not to have occurred https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-serial-4.1/818#openshift-tests-sig-scheduling-schedulerpriorities-serial-pod-should-avoid-nodes-that-have-avoidpod-annotation-suiteopenshiftconformanceserial-suitek8s This is likely not a 4.1 blocker, but we need to know why this happened. If this is just a bug in the test, it's probably a medium. But on the off chance this is an actual scheduler bug (the cluster is idle) and avoidPod might be used on the control plane, needs investigation.
Upstream PR: https://github.com/kubernetes/kubernetes/pull/84513
Checked recently e2e run, this problem seem disappear.
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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0062