origin: flake: registry returns unauthorized: authentication required when pushing origin image

Seen here: https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/18957/test_pull_request_origin_extended_conformance_gce/17585/

and https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/18948/test_pull_request_origin_extended_conformance_gce/17584/

[WARNING] Pushing local :13b98b9 images to registry.svc.ci.openshift.org/*:v3.9,:v3.9.0
[INFO] Pushing registry.svc.ci.openshift.org/openshift/origin:v3.9...
The push refers to a repository [registry.svc.ci.openshift.org/openshift/origin]
59bf1254fb1c: Preparing
54f01455206c: Preparing
578db27597cd: Preparing
b03095563b79: Preparing
unauthorized: authentication required
[ERROR] PID 5795: hack/push-release.sh:76: `docker push ${PUSH_OPTS} "${OS_PUSH_BASE_REGISTRY-}${image}${tag}"` exited with status 1.

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 23 (23 by maintainers)

Most upvoted comments

unfortunately the text @stevekuznetsov grepped on is expected output from our tests:

Running test/end-to-end/core.sh:321: executing 'docker push '172.30.1.1:5000/missing/image:tag'' expecting failure and text 'authentication required'...
SUCCESS after 0.083s: test/end-to-end/core.sh:321: executing 'docker push '172.30.1.1:5000/missing/image:tag'' expecting failure and text 'authentication required'
Standard output from the command:
The push refers to a repository [172.30.1.1:5000/missing/image]
c5183829c43c: Preparing

Standard error from the command:
unauthorized: authentication required

So do we actually have evidence of a build/job that failed due to push issues lately?

bparees on Mar 21, 2018