Bug 2065454

Summary: openshift-tests-upgrade.[sig-scheduling][Early] The openshift-etcd pods should be scheduled on different nodes [Suite:openshift/conformance/parallel]
Product: OpenShift Container Platform Reporter: W. Trevor King <wking>
Component: kube-schedulerAssignee: ravig <rgudimet>
Status: CLOSED DUPLICATE QA Contact: RamaKasturi <knarra>
Severity: high Docs Contact:
Priority: high    
Version: 4.11CC: aos-bugs, mfojtik, sippy
Target Milestone: ---   
Target Release: ---   
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: 2022-03-21 22:17:28 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 W. Trevor King 2022-03-17 21:10:19 UTC 
openshift-tests-upgrade.[sig-scheduling][Early] The openshift-etcd pods should be scheduled on different nodes [Suite:openshift/conformance/parallel]

is failing frequently in CI, see:

$ w3m -dump -cols 200 'https://search.ci.openshift.org/?type=junit&search=openshift-etcd+pods+should+be+scheduled+on+different+nodes' | grep 'failures match' | sort
aggregated-aws-sdn-upgrade-4.11-micro-release-openshift-release-analysis-aggregator (all) - 7 runs, 43% failed, 33% of failures match = 14% impact
aggregator-periodic-ci-openshift-release-master-ci-4.11-e2e-aws-ovn-upgrade (all) - 3 runs, 100% failed, 67% of failures match = 67% impact
aggregator-periodic-ci-openshift-release-master-ci-4.11-e2e-azure-ovn-upgrade (all) - 3 runs, 100% failed, 67% of failures match = 67% impact
aggregator-periodic-ci-openshift-release-master-ci-4.11-upgrade-from-stable-4.10-e2e-aws-ovn-upgrade (all) - 3 runs, 100% failed, 33% of failures match = 33% impact
aggregator-periodic-ci-openshift-release-master-ci-4.11-upgrade-from-stable-4.10-e2e-azure-upgrade (all) - 3 runs, 100% failed, 67% of failures match = 67% impact
aggregator-periodic-ci-openshift-release-master-ci-4.11-upgrade-from-stable-4.10-e2e-gcp-ovn-upgrade (all) - 3 runs, 100% failed, 33% of failures match = 33% impact
aggregator-periodic-ci-openshift-release-master-nightly-4.11-e2e-aws-upgrade (all) - 3 runs, 67% failed, 50% of failures match = 33% impact
periodic-ci-openshift-multiarch-master-nightly-4.11-ocp-e2e-aws-arm64-techpreview (all) - 11 runs, 64% failed, 14% of failures match = 9% impact
periodic-ci-openshift-multiarch-master-nightly-4.11-ocp-e2e-aws-ovn-arm64 (all) - 11 runs, 27% failed, 33% of failures match = 9% impact
periodic-ci-openshift-release-master-ci-4.11-e2e-aws-cgroupsv2 (all) - 16 runs, 56% failed, 11% of failures match = 6% impact
periodic-ci-openshift-release-master-ci-4.11-e2e-aws-ovn (all) - 7 runs, 57% failed, 25% of failures match = 14% impact
periodic-ci-openshift-release-master-ci-4.11-e2e-aws-ovn-upgrade (all) - 140 runs, 60% failed, 5% of failures match = 3% impact
periodic-ci-openshift-release-master-ci-4.11-e2e-aws-serial (all) - 13 runs, 38% failed, 20% of failures match = 8% impact
periodic-ci-openshift-release-master-ci-4.11-e2e-azure (all) - 2 runs, 100% failed, 50% of failures match = 50% impact
periodic-ci-openshift-release-master-ci-4.11-e2e-azure-ovn-upgrade (all) - 70 runs, 74% failed, 2% of failures match = 1% impact
periodic-ci-openshift-release-master-ci-4.11-e2e-gcp-ovn (all) - 7 runs, 57% failed, 25% of failures match = 14% impact
periodic-ci-openshift-release-master-ci-4.11-e2e-gcp-techpreview-serial (all) - 7 runs, 71% failed, 20% of failures match = 14% impact
periodic-ci-openshift-release-master-ci-4.11-e2e-gcp-upgrade (all) - 154 runs, 50% failed, 6% of failures match = 3% impact
periodic-ci-openshift-release-master-ci-4.11-upgrade-from-stable-4.10-e2e-aws-ovn-upgrade (all) - 154 runs, 55% failed, 4% of failures match = 2% impact
periodic-ci-openshift-release-master-ci-4.11-upgrade-from-stable-4.10-e2e-azure-upgrade (all) - 139 runs, 83% failed, 1% of failures match = 1% impact
periodic-ci-openshift-release-master-ci-4.11-upgrade-from-stable-4.10-e2e-ovirt-upgrade (all) - 8 runs, 75% failed, 17% of failures match = 13% impact
periodic-ci-openshift-release-master-nightly-4.11-e2e-aws-cgroupsv2 (all) - 16 runs, 25% failed, 50% of failures match = 13% impact
periodic-ci-openshift-release-master-nightly-4.11-e2e-aws-crun (all) - 16 runs, 50% failed, 38% of failures match = 19% impact
periodic-ci-openshift-release-master-nightly-4.11-e2e-aws-serial (all) - 14 runs, 57% failed, 13% of failures match = 7% impact
periodic-ci-openshift-release-master-nightly-4.11-e2e-aws-upgrade (all) - 77 runs, 66% failed, 8% of failures match = 5% impact
periodic-ci-openshift-release-master-nightly-4.11-e2e-gcp (all) - 7 runs, 43% failed, 33% of failures match = 14% impact
periodic-ci-openshift-release-master-nightly-4.11-e2e-metal-ipi-ovn-ipv6 (all) - 19 runs, 84% failed, 38% of failures match = 32% impact
periodic-ci-openshift-release-master-nightly-4.11-e2e-ovirt (all) - 15 runs, 53% failed, 13% of failures match = 7% impact
periodic-ci-openshift-release-master-nightly-4.11-e2e-vsphere-techpreview-serial (all) - 11 runs, 36% failed, 25% of failures match = 9% impact
periodic-ci-openshift-release-master-nightly-4.11-upgrade-from-stable-4.10-e2e-aws-upgrade (all) - 7 runs, 57% failed, 25% of failures match = 14% impact
pull-ci-openshift-cluster-baremetal-operator-master-e2e-metal-ipi-ovn-ipv6 (all) - 5 runs, 80% failed, 25% of failures match = 20% impact
...

Example run [1]:

: [sig-scheduling][Early] The openshift-etcd pods should be scheduled on different nodes [Suite:openshift/conformance/parallel]
Run #0: Failed	5s

  {  fail [github.com/openshift/origin/test/extended/scheduling/pods.go:151]: Mar 15 23:11:29.230: ns/openshift-etcd pod etcd-quorum-guard-85645b858f-p4g5b and pod etcd-quorum-guard-85645b858f-8m7f2 are running on the same node: ci-op-yy522z6c-09380-hn4d5-master-0}

Might be a dup of bug 2062459.

[1]: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.11-e2e-gcp/1503862873753915392
Comment 1 W. Trevor King 2022-03-21 22:17:28 UTC 
Bug 2063831 is covering this same test-case.  I've just updated its Environment property, so the bug turns up in a Sippy search [1], and I'm closing this one as a dup.

[1]: https://search.ci.openshift.org/?type=bug&search=openshift-etcd+pods+should+be+scheduled+on+different+nodes

*** This bug has been marked as a duplicate of bug 2063831 ***