Bug 1724332 - Test flake - Pod should be preferably scheduled to nodes pod can tolerate
Summary: Test flake - Pod should be preferably scheduled to nodes pod can tolerate
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-scheduler
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.2.0
Assignee: Mike Dame
QA Contact: Xingxing Xia
URL:
Whiteboard: buildcop
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-26 19:47 UTC by Mark McLoughlin
Modified: 2019-10-30 20:28 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-22 06:06:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin pull 23544 0 None closed Bug 1724332: Toleration priority function score computation 2021-01-14 15:59:59 UTC
Github openshift origin pull 23627 0 None closed Bug 1724332: Fix upstream scheduler taints/tolerations e2e 2021-01-14 15:59:59 UTC

Description Mark McLoughlin 2019-06-26 19:47:22 UTC
Description of problem:

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-serial-4.2/1281
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-serial-4.2/1261
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-serial-4.1/913


[sig-scheduling] SchedulerPriorities [Serial] Pod should be preferably scheduled to nodes pod can tolerate [Suite:openshift/conformance/serial] [Suite:k8s] expand_less	2m15s
fail [k8s.io/kubernetes/test/e2e/scheduling/priorities.go:256]: Expected
    <string>: ip-10-0-152-102.ec2.internal
to equal
    <string>: ip-10-0-141-48.ec2.internal


Version-Release number of selected component (if applicable):

both 4.1 and 4.2 jobs


How reproducible:

Seen at least 3 times in the last 24 hours

Comment 2 ravig 2019-08-02 23:52:49 UTC
The PR should be address the issue now

https://github.com/openshift/origin/pull/23544

Lowering the severity since this is test suite issue.

Comment 4 W. Trevor King 2019-08-13 22:16:02 UTC
Maciej, I see you set Target Release to 4.2.0 on 2019-06-27.  Looks like Mark opened this with Version 4.1.0.  I dunno if that's a compatible pairing.  If this bug affects both 4.1 and 4.2 (seems like it does), this should probably be Version 4.2.0.  If we decide it needs a 4.1.z backport, we should clone a new bug with a 4.1.z Version and 4.1.z Target Release.  Or am I misunderstanding our Bugzilla flow?

Also, should this bug move back to ASSIGNED now that https://github.com/openshift/origin/pull/23592 reverted https://github.com/openshift/origin/pull/23544 ?

Comment 5 Mike Dame 2019-08-15 15:28:55 UTC
This is being revisited in https://github.com/kubernetes/kubernetes/pull/81472/

Comment 6 Mike Dame 2019-08-19 15:01:27 UTC
New upstream fix carried in https://github.com/openshift/origin/pull/23627

Comment 7 Xingxing Xia 2019-08-22 06:06:46 UTC
Above PR fixed file is under .../test/e2e/scheduling/...
Above failure is gone and the case is green (from #3451 till latest #3573 as of now in "https://testgrid.k8s.io/redhat-openshift-release-blocking#redhat-release-openshift-origin-installer-e2e-aws-serial-4.2&sort-by-flakiness=" ).
So changing bug status.

Comment 8 Maciej Szulik 2019-10-30 20:28:45 UTC
This fix will not be backported to 4.1.


Note You need to log in before you can comment on or make changes to this bug.