Job:
#1925941bug6 months ago[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] CLOSED
Bug 1925941: [sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial]
Status: CLOSED
#1896558bug5 months ago[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] CLOSED
Bug 1896558: [sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial]
Status: CLOSED
test:
[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial]
release-openshift-ocp-installer-e2e-azure-serial-4.12 (all) - 52 runs, 52% failed, 4% of failures match = 2% impact
#1553651015163580416junit7 days ago
[sig-network][Feature:EgressIP] [external-targets] pods should have the assigned EgressIPs and EgressIPs can be updated [Skipped:Network/OpenShiftSDN] [Serial] [Suite:openshift/conformance/serial]
[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]
#1553651015163580416junit7 days ago
# [sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]
fail [k8s.io/kubernetes@v1.24.0/test/e2e/scheduling/ubernetes_lite.go:191]: Pods were not evenly spread across zones.  0 in one zone and 8 in another zone
#1553651015163580416junit7 days ago
Jul 31 08:52:53.894 - 7780s E alert/Watchdog ns/openshift-monitoring ALERTS{alertname="Watchdog", alertstate="firing", namespace="openshift-monitoring", prometheus="openshift-monitoring/k8s", severity="none"}
Jul 31 09:17:07.562 - 72s   E e2e-test/"[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]" e2e test finished As "Failed"
Jul 31 10:22:56.053 - 25s   E clusteroperator/authentication condition/Available status/False reason/APIServicesAvailable: "oauth.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request\nAPIServicesAvailable: "user.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request

Found in 1.92% of runs (3.70% of failures) across 52 total runs and 1 jobs (51.92% failed) in 302ms - clear search | chart view - source code located on github