Bug 1700458

Summary: e2e flake: SchedulerPreemption tests fails with 'pods "pod0-sched-preemption-low-priority" not found'
Product: OpenShift Container Platform Reporter: Seth Jennings <sjenning>
Component: NodeAssignee: ravig <rgudimet>
Status: CLOSED ERRATA QA Contact: Sunil Choudhary <schoudha>
Severity: high Docs Contact:
Priority: high    
Version: 4.1.0CC: aos-bugs, jokerman, mmccomas, rgudimet, schoudha
Target Milestone: ---   
Target Release: 4.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-04 10:47:40 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:

Description Seth Jennings 2019-04-16 15:33:09 UTC 
https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-serial-4.0/3970

https://search.svc.ci.openshift.org/?search=SchedulerPreemption&maxAge=168h&context=2&type=all

example failure output

fail [k8s.io/kubernetes/test/e2e/scheduling/preemption.go:163]: Expected error:
    <*errors.StatusError | 0xc42250e990>: {
        ErrStatus: {
            TypeMeta: {Kind: "", APIVersion: ""},
            ListMeta: {SelfLink: "", ResourceVersion: "", Continue: ""},
            Status: "Failure",
            Message: "pods \"pod0-sched-preemption-low-priority\" not found",
            Reason: "NotFound",
            Details: {
                Name: "pod0-sched-preemption-low-priority",
                Group: "",
                Kind: "pods",
                UID: "",
                Causes: nil,
                RetryAfterSeconds: 0,
            },
            Code: 404,
        },
    }
    pods "pod0-sched-preemption-low-priority" not found
not to have occurred
Comment 8 errata-xmlrpc 2019-06-04 10:47:40 UTC 
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-2019:0758
Comment 9 Red Hat Bugzilla 2023-09-14 05:27:01 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days