Description of problem: Not sure what's causing this, but the registry seems down for me. Maybe this will fix itself over time (?) but for now, I'm stuck. Trying a new build gives the same result. I've been getting this result for 20 minutes or so, so I'm starting to feel this will not auto-heal. Version-Release number of selected component (if applicable): OpenShift Online developer preview How reproducible: Steps to Reproduce: 1. Start build 2. Get coffee 3. Find failed build Actual results: I0622 10:38:22.059876 1 sti.go:268] Using provided push secret for pushing 172.30.47.227:5000/casa-san-pietro/django-psql-example:latest image I0622 10:38:22.059905 1 sti.go:272] Pushing 172.30.47.227:5000/casa-san-pietro/django-psql-example:latest image ... E0622 10:38:29.741794 1 dockerutil.go:86] push for image 172.30.47.227:5000/casa-san-pietro/django-psql-example:latest failed, will retry in 5s ... E0622 10:38:41.765705 1 dockerutil.go:86] push for image 172.30.47.227:5000/casa-san-pietro/django-psql-example:latest failed, will retry in 5s ... E0622 10:38:53.807630 1 dockerutil.go:86] push for image 172.30.47.227:5000/casa-san-pietro/django-psql-example:latest failed, will retry in 5s ... E0622 10:39:07.861680 1 dockerutil.go:86] push for image 172.30.47.227:5000/casa-san-pietro/django-psql-example:latest failed, will retry in 5s ... E0622 10:39:21.927610 1 dockerutil.go:86] push for image 172.30.47.227:5000/casa-san-pietro/django-psql-example:latest failed, will retry in 5s ... E0622 10:39:35.985310 1 dockerutil.go:86] push for image 172.30.47.227:5000/casa-san-pietro/django-psql-example:latest failed, will retry in 5s ... E0622 10:39:50.051595 1 dockerutil.go:86] push for image 172.30.47.227:5000/casa-san-pietro/django-psql-example:latest failed, will retry in 5s ... I0622 10:39:55.051884 1 sti.go:277] Registry server Address: I0622 10:39:55.051926 1 sti.go:278] Registry server User Name: serviceaccount I0622 10:39:55.051935 1 sti.go:279] Registry server Email: serviceaccount I0622 10:39:55.051942 1 sti.go:284] Registry server Password: <<non-empty>> F0622 10:39:55.051959 1 builder.go:204] Error: build error: Failed to push image. Response from registry is: unable to ping registry endpoint https://172.30.47.227:5000/v0/ v2 ping attempt failed with error: Get https://172.30.47.227:5000/v2/: dial tcp 172.30.47.227:5000: no route to host v1 ping attempt failed with error: Get https://172.30.47.227:5000/v1/_ping: dial tcp 172.30.47.227:5000: no route to host Expected results: Image uploads to registry, gets deployed. Additional info:
Same problem for me. 1) Created a new Project 2) Created a new Image to build from a Github URL 3) The initial build started automatically 4) The build failed Re-building doesn't help, and I get the same exact error, with the same hostname: F0622 11:20:25.725435 1 builder.go:204] Error: build error: Failed to push image. Response from registry is: unable to ping registry endpoint https://172.30.47.227:5000/v0/ v2 ping attempt failed with error: Get https://172.30.47.227:5000/v2/: dial tcp 172.30.47.227:5000: no route to host v1 ping attempt failed with error: Get https://172.30.47.227:5000/v1/_ping: dial tcp 172.30.47.227:5000: no route to host The system status at http://status.preview.openshift.com/ shows that all systems are operational, including the Docker Registry.
And in the meantime it _did_ selfheal...
Maxim, can you try again now? We think the issue that caused this may be resolved now.
Hi Ben, as said in comment #2, it self healed after about thirty minutes. In the meantime, I've been able to do 30-odd builds and deployments, which all worked fine ever since.
Thanks Maxim