Bug 1717198

Summary: scheduling e2e: reenable SchedulerPreemption tests
Product: OpenShift Container Platform Reporter: Seth Jennings <sjenning>
Component: kube-schedulerAssignee: ravig <rgudimet>
Status: CLOSED ERRATA QA Contact: ge liu <geliu>
Severity: high Docs Contact:
Priority: high    
Version: 4.2.0CC: aos-bugs, jokerman, maszulik, mfojtik, mmccomas, wking
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:31:10 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-06-04 21:21:19 UTC
After Prometheus starting making reasonable memory requests, the assumptions that the SchedulerPreemption tests make about the schedule load on test nodes does not hold (i.e. less than 40% of capacity is scheduled).

Need to rework this test and reenable.

Comment 1 Seth Jennings 2019-06-04 21:28:06 UTC
PR to revert when test is fixed
https://github.com/openshift/origin/pull/23029

Comment 2 W. Trevor King 2019-06-11 10:55:13 UTC
We'll also want to revert https://github.com/openshift/release/pull/4027 if it lands.

Comment 4 Maciej Szulik 2019-08-08 12:55:42 UTC
The test is re-enabled so I guess the BZ can be closed now. If the other part is required, please open a new one.

Comment 6 errata-xmlrpc 2019-10-16 06:31:10 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:2922

Comment 7 W. Trevor King 2020-05-17 04:31:48 UTC
Bug is CLOSED ERRATA.  Nobody needs info on it anymore (or if they do, they should comment again with the information they still need).