Bug 1724332

Summary:	Test flake - Pod should be preferably scheduled to nodes pod can tolerate
Product:	OpenShift Container Platform	Reporter:	Mark McLoughlin <markmc>
Component:	kube-scheduler	Assignee:	Mike Dame <mdame>
Status:	CLOSED WORKSFORME	QA Contact:	Xingxing Xia <xxia>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	aos-bugs, geliu, maszulik, mfojtik, rgudimet, wking
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	buildcop
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-22 06:06:46 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 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 1 Adam Kaplan 2019-07-01 20:24:52 UTC

Also observed here:
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-serial-4.2/1431
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-serial-4.2/1429

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.