origin: Failed to push image: received unexpected HTTP status: 500 Internal Server Error

** Build Logs:
Apr 28 09:29:35.505: INFO: Running 'oc logs --config=/tmp/extended-test-docker-build-pullsecret-xtfpn-rrtrw-user.kubeconfig --namespace=extended-test-docker-build-pullsecret-xtfpn-rrtrw -f build/docker-build-1 --timestamps'
2017-04-28T13:29:02.894130000Z Pulling image centos:7 ...
2017-04-28T13:29:04.636081000Z Step 1 : FROM centos:7
2017-04-28T13:29:04.638434000Z  ---> a8493f5f50ff
2017-04-28T13:29:04.638941000Z Step 2 : ENV "OPENSHIFT_BUILD_NAME" "docker-build-1" "OPENSHIFT_BUILD_NAMESPACE" "extended-test-docker-build-pullsecret-xtfpn-rrtrw"
2017-04-28T13:29:04.699505000Z  ---> Running in 7337cde2edba
2017-04-28T13:29:04.773734000Z  ---> dae979935ad0
2017-04-28T13:29:04.778713000Z Removing intermediate container 7337cde2edba
2017-04-28T13:29:04.778998000Z Step 3 : LABEL "io.openshift.build.namespace" "extended-test-docker-build-pullsecret-xtfpn-rrtrw" "io.openshift.build.name" "docker-build-1"
2017-04-28T13:29:04.842527000Z  ---> Running in 47d20745dbdd
2017-04-28T13:29:04.902307000Z  ---> ecbdd4847ec7
2017-04-28T13:29:04.912445000Z Removing intermediate container 47d20745dbdd
2017-04-28T13:29:04.912790000Z Successfully built ecbdd4847ec7
2017-04-28T13:29:04.930863000Z Pushing image 172.30.182.180:5000/extended-test-docker-build-pullsecret-xtfpn-rrtrw/image1:latest ...
2017-04-28T13:29:07.355698000Z Pushed 0/1 layers, 3% complete
2017-04-28T13:29:27.647590000Z Pushed 1/1 layers, 100% complete
2017-04-28T13:29:31.043858000Z Registry server Address: 
2017-04-28T13:29:31.044263000Z Registry server User Name: serviceaccount
2017-04-28T13:29:31.044454000Z Registry server Email: serviceaccount@example.org
2017-04-28T13:29:31.044631000Z Registry server Password: <<non-empty>>
2017-04-28T13:29:31.044815000Z error: build error: Failed to push image: received unexpected HTTP status: 500 Internal Server Error

https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin/503

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 16 (9 by maintainers)

Most upvoted comments

@malagant i’m afraid that’s just one of many potential causes of 500 errors from the registry, but i’m glad you were able to sort yours out!

bparees on Oct 16, 2017

I had the same problem, I fixed it by disabling validation. docker run -d -p 5000:5000 --name registry -e REGISTRY_VALIDATION_DISABLED=true registry:2

alpharameeztech on Sep 8, 2020

I also faced the same error, in my case the registry was full. So I added archival policy to the images and made some space, it solved my problem.

nehagup on Jul 18, 2019

In my case it was memory issue , i cleared some space and the image is pushed successfully . i was trying to push a 16 gb windows image .

anil120 on Oct 11, 2019

I had this issue, too today. Just a hint with a great solution if you’re having this (works also with 3.6)

https://access.redhat.com/solutions/2173071#comments

TL;DR: It’s all about permissions.

malagant on Oct 15, 2017