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
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
The PR should be address the issue now https://github.com/openshift/origin/pull/23544 Lowering the severity since this is test suite issue.
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 ?
This is being revisited in https://github.com/kubernetes/kubernetes/pull/81472/
New upstream fix carried in https://github.com/openshift/origin/pull/23627
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.
This fix will not be backported to 4.1.