Description of problem: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-azure-4.2/96 Version-Release number of selected component (if applicable): release-openshift-ocp-installer-e2e-azure-4.2 [Conformance][Area:Networking][Feature:Router] The HAProxy router converges when multiple routers are writing status [Suite:openshift/conformance/parallel/minimal] Oct 15 16:57:06.740: INFO: Error running &{/usr/bin/oc [oc --namespace=e2e-test-router-stress-mfvgj --config=/tmp/admin.kubeconfig logs pod/router-mzzbb -c router -n e2e-test-router-stress-mfvgj] [] Error from server (BadRequest): container "router" in pod "router-mzzbb" is waiting to start: trying and failing to pull image Error from server (BadRequest): container "router" in pod "router-mzzbb" is waiting to start: trying and failing to pull image [] <nil> 0xc0030811a0 exit status 1 <nil> <nil> true [0xc00367a1e0 0xc00367a218 0xc00367a218] [0xc00367a1e0 0xc00367a218] [0xc00367a1f0 0xc00367a208] [0x95aef0 0x95b020] 0xc00228c000 <nil>}: Error from server (BadRequest): container "router" in pod "router-mzzbb" is waiting to start: trying and failing to pull image Oct 15 16:57:06.740: INFO: Error retrieving logs for pod "router-mzzbb"/"router": exit status 1 fail [github.com/openshift/origin/test/extended/router/stress.go:90]: Unexpected error: <*errors.errorString | 0xc002726fd0>: { s: "replicaset \"router\" never became ready", } replicaset "router" never became ready occurred
Looks like the router image used for the custom router deployment tests is coming from.... dockerhub?! Normal Pulling 73s (x4 over 2m52s) kubelet, ci-op-jbq4vvz0-37d82-djhmk-worker-centralus3-98qqc Pulling image "openshift/origin-haproxy-router:latest" Warning Failed 73s (x4 over 2m51s) kubelet, ci-op-jbq4vvz0-37d82-djhmk-worker-centralus3-98qqc Failed to pull image "openshift/origin-haproxy-router:latest": rpc error: code = Unknown desc = pinging docker registry returned: error pinging registry registry-1.docker.io, response code 503 (Service Unavailable) Also, that pull spec looks highly suspicious and suggests we're not actually testing the router image being used in the release payload.
didn't see this issue since https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-azure-4.3/297
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0062