Bug 1713134
| Summary: | AvoidPod serial e2e test has flaked | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Clayton Coleman <ccoleman> |
| Component: | kube-scheduler | Assignee: | Jan Chaloupka <jchaloup> |
| Status: | CLOSED ERRATA | QA Contact: | ge liu <geliu> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.0 | CC: | aos-bugs, gblomqui, jokerman, maszulik, mfojtik, mmccomas, rgudimet |
| Target Milestone: | --- | ||
| Target Release: | 4.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-01-23 11:03:45 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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 |
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.