#9536 openshift build failing with PushImageToRegistryFailed
Closed: Fixed 3 years ago by kevin. Opened 3 years ago by darknao.

The docstranslation build failed to push image to internal registry :

Successfully built 9cb13785073f
I1216 17:35:33.501599       1 cfg.go:39] Locating docker auth for image docker-registry.default.svc:5000/docstranslation/builder:latest and type PUSH_DOCKERCFG_PATH
I1216 17:35:33.501623       1 cfg.go:49] Getting docker auth in paths : [/var/run/secrets/openshift.io/push]
I1216 17:35:33.501663       1 config.go:131] looking for config.json at /var/run/secrets/openshift.io/push/config.json
I1216 17:35:33.501706       1 config.go:101] looking for .dockercfg at /var/run/secrets/openshift.io/push/.dockercfg
I1216 17:35:33.501964       1 config.go:112] found .dockercfg at /var/run/secrets/openshift.io/push/.dockercfg
I1216 17:35:33.501998       1 cfg.go:62] Using serviceaccount user for Docker authentication for image docker-registry.default.svc:5000/docstranslation/builder:latest
I1216 17:35:33.502025       1 builder.go:240] Authenticating Docker push with user "serviceaccount"

Pushing image docker-registry.default.svc:5000/docstranslation/builder:latest ...
The push refers to a repository [docker-registry.default.svc:5000/docstranslation/builder] 
Preparing
Preparing
Preparing
Preparing
Registry server Address: 
Registry server User Name: serviceaccount
Registry server Email: serviceaccount@example.org
Registry server Password: <<non-empty>>
F1216 17:35:33.700334       1 helpers.go:119] error: build error: Failed to push image: unauthorized: authentication required

I'm don't know why this is happening, but maybe someone can either remove/recreate the builder serviceaccount in this namespace, or just remove the complete namespace and replay the playbook (playbooks/openshift-apps/docstranslation.yml).


Metadata Update from @smooge:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: OpenShift, medium-gain, medium-trouble, ops

3 years ago

deleting / recreating the entire project did the trick.

Metadata Update from @darknao:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Issue status updated to: Open (was: Closed)

3 years ago

Issue status updated to: Closed (was: Open)
Issue close_status updated to: Fixed

3 years ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Done