Job:
#1925941bug5 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
#1896558bug3 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) - 25 runs, 40% failed, 10% of failures match = 4% impact
#1542552819310006272junit27 hours ago
[sig-network][Feature:EgressIP] [external-targets] pods should keep the assigned EgressIPs when being rescheduled to another node [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]
#1542552819310006272junit27 hours 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
#1542552819310006272junit27 hours ago
Jun 30 18:20:04.282 E ns/e2e-daemonsets-7662 pod/daemon-set-cqrq6 node/ci-op-4klgf4ls-b6987-9bxx2-worker-eastus23-lxk8r uid/5b92b9e7-1760-49de-8c10-175a2658ff4f container/app reason/ContainerExit code/137 cause/ContainerStatusUnknown The container could not be located when the pod was terminated
Jun 30 18:21:23.504 - 70s   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"
Jun 30 18:21:29.796 E ns/e2e-sched-pred-6646 pod/pod2 node/ci-op-4klgf4ls-b6987-9bxx2-worker-eastus23-lxk8r uid/da2eb7bf-8550-4aee-9377-01f3601229df container/agnhost reason/ContainerExit code/2 cause/Error
#1542552819310006272junit27 hours ago
Jun 30 18:21:30.847 E ns/e2e-sched-pred-6646 pod/pod1 node/ci-op-4klgf4ls-b6987-9bxx2-worker-eastus23-lxk8r uid/d772fb32-89c3-4cde-b701-6ba64cfc5555 container/agnhost reason/ContainerExit code/2 cause/Error
Jun 30 18:22:33.507 E e2e-test/"[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]" finishedStatus/Failed
Jun 30 18:22:39.469 E ns/e2e-multi-az-8531 pod/test-service-3 node/ci-op-4klgf4ls-b6987-9bxx2-worker-eastus23-lxk8r uid/ea8a7cb2-62d0-4739-bd0d-e0292e6c0caa container/test-service-3 reason/ContainerExit code/137 cause/ContainerStatusUnknown The container could not be located when the pod was deleted.  The container used to be Running
periodic-ci-openshift-release-master-ci-4.8-e2e-aws-serial (all) - 16 runs, 13% failed, 50% of failures match = 6% impact
#1542216314335006720junit2 days ago
[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]
#1542216314335006720junit2 days ago
[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]
#1542216314335006720junit2 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.21.1/test/e2e/scheduling/ubernetes_lite.go:190]: Pods were not evenly spread across zones.  2 in one zone and 8 in another zone
#1542216314335006720junit2 days ago
Jun 29 19:52:50.895 E ns/openshift-ingress-canary pod/ingress-canary-jngmv node/ip-10-0-166-95.ec2.internal container/serve-healthcheck-canary reason/ContainerExit code/2 cause/Error serving on 8888\nserving on 8080\nServing canary healthcheck request\nServing canary healthcheck request\n
Jun 29 20:00:11.497 - 82s   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"
Jun 29 20:01:33.812 E e2e-test/"[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]" finishedStatus/Failed
Jun 29 20:06:56.490 E clusteroperator/dns condition/Degraded status/True reason/DNSDegraded changed: DNS default is degraded
periodic-ci-openshift-release-master-ci-4.12-e2e-gcp-techpreview-serial (all) - 25 runs, 64% failed, 6% of failures match = 4% impact
#1541925284763144192junit2 days ago
[sig-instrumentation][Late] Alerts shouldn't report any unexpected alerts in firing or pending state [Suite:openshift/conformance/parallel]
[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]
#1541925284763144192junit2 days ago
[sig-instrumentation][Late] Alerts shouldn't report any unexpected alerts in firing or pending state [Suite:openshift/conformance/parallel]
[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]
#1541925284763144192junit2 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
#1541925284763144192junit2 days ago
Jun 29 00:31:28.171 E ns/e2e-daemonsets-4886 pod/daemon-set-85mp4 node/ci-op-gi4dr3dr-4b441-lmj67-worker-b-vw5vz uid/3640dc10-87d8-40ec-b131-a70dbc909dc8 reason/Failed ():
Jun 29 00:31:36.931 - 71s   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"
Jun 29 00:32:48.139 E e2e-test/"[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]" finishedStatus/Failed
Jun 29 00:41:47.156 E ns/e2e-volumelimits-7928-414 pod/csi-hostpathplugin-0 node/ci-op-gi4dr3dr-4b441-lmj67-worker-b-vw5vz uid/e7fdb2ef-be27-4f21-8d87-13a32b752ea5 container/csi-attacher reason/ContainerExit code/2 cause/Error
periodic-ci-openshift-release-master-ci-4.11-e2e-gcp-techpreview-serial (all) - 11 runs, 91% failed, 10% of failures match = 9% impact
#1541743652076785664junit3 days ago
[sig-instrumentation][Late] Alerts shouldn't report any unexpected alerts in firing or pending state [Suite:openshift/conformance/parallel]
[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]
#1541743652076785664junit3 days ago
[sig-instrumentation][Late] Alerts shouldn't report any unexpected alerts in firing or pending state [Suite:openshift/conformance/parallel]
[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]
#1541743652076785664junit3 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
#1541743652076785664junit3 days ago
Jun 28 12:20:23.963 - 999ms E ns/openshift-authentication route/oauth-openshift disruption/ingress-to-oauth-server connection/reused reason/DisruptionBegan ns/openshift-authentication route/oauth-openshift disruption/ingress-to-oauth-server connection/reused stopped responding to GET requests over reused connections: Get "https://oauth-openshift.apps.ci-op-4kpi5zx9-234d7.XXXXXXXXXXXXXXXXXXXXXX/healthz": net/http: timeout awaiting response headers
Jun 28 12:20:27.550 - 73s   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"
Jun 28 12:21:40.609 E e2e-test/"[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]" finishedStatus/Failed
Jun 28 12:26:48.332 E ns/e2e-sched-preemption-1197 pod/pod1-1-sched-preemption-medium-priority node/ci-op-4kpi5zx9-234d7-cl62n-worker-b-kcbtx uid/ce78b19e-3434-4c1b-8d3f-8fb2478bf1ae container/pod1-1-sched-preemption-medium-priority reason/ContainerExit code/137 cause/ContainerStatusUnknown The container could not be located when the pod was deleted.  The container used to be Running
periodic-ci-openshift-release-master-nightly-4.10-e2e-aws-fips-serial (all) - 4 runs, 25% failed, 100% of failures match = 25% impact
#1540781336304816128junit6 days ago
[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]
#1540781336304816128junit6 days ago
[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]
#1540781336304816128junit6 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.23.0/test/e2e/scheduling/ubernetes_lite.go:190]: Pods were not evenly spread across zones.  0 in one zone and 10 in another zone
#1540781336304816128junit6 days ago
Jun 25 20:53:22.671 E ns/e2e-daemonsets-3394 pod/daemon-set-w52m5 node/ip-10-0-197-66.ec2.internal container/app reason/ContainerExit code/137 cause/ContainerStatusUnknown The container could not be located when the pod was terminated
Jun 25 20:53:32.993 - 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"
Jun 25 20:54:45.025 E e2e-test/"[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]" finishedStatus/Failed
Jun 25 20:58:42.511 E ns/openshift-monitoring pod/thanos-querier-f55967c4f-nxdls node/ip-10-0-138-154.ec2.internal container/oauth-proxy reason/ContainerExit code/2 cause/Error 2022/06/25 20:10:07 provider.go:129: Defaulting client-id to system:serviceaccount:openshift-monitoring:thanos-querier\n2022/06/25 20:10:07 provider.go:134: Defaulting client-secret to service account token /var/run/secrets/kubernetes.io/serviceaccount/token\n2022/06/25 20:10:07 provider.go:358: Delegation of authentication and authorization to OpenShift is enabled for bearer tokens and client certificates.\n2022/06/25 20:10:14 oauthproxy.go:203: mapping path "/" => upstream "http://localhost:9090/"\n2022/06/25 20:10:14 oauthproxy.go:224: compiled skip-auth-regex => "^/-/(healthy|ready)$"\n2022/06/25 20:10:14 oauthproxy.go:230: OAuthProxy configured for  Client ID: system:serviceaccount:openshift-monitoring:thanos-querier\n2022/06/25 20:10:14 oauthproxy.go:240: Cookie settings: name:_oauth_proxy secure(https):true httponly:true expiry:168h0m0s domain:<default> samesite: refresh:disabled\n2022/06/25 20:10:14 main.go:156: using htpasswd file /etc/proxy/htpasswd/auth\nI0625 20:10:14.536379       1 dynamic_serving_content.go:130] Starting serving::/etc/tls/private/tls.crt::/etc/tls/private/tls.key\n2022/06/25 20:10:14 http.go:107: HTTPS: listening on [::]:9091\n
periodic-ci-openshift-release-master-nightly-4.7-e2e-gcp-fips-serial (all) - 4 runs, 75% failed, 33% of failures match = 25% impact
#1540781587900141568junit6 days ago
[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]
#1540781587900141568junit6 days ago
[sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones [Serial] [Suite:openshift/conformance/serial] [Suite:k8s]
#1540781587900141568junit6 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.20.0/test/e2e/scheduling/ubernetes_lite.go:174]: Pods were not evenly spread across zones.  1 in one zone and 7 in another zone

Found in 0.00% of runs (0.02% of failures) across 123488 total runs and 6215 jobs (22.58% failed) in 490ms - clear search | chart view - source code located on github