[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: build failing with "v2 ping attempt failed with error:" message



Thanks Ben for the reply,sorry last night i crashed out before sending the details:

 infrastructure:
running 3 nodes and 1 master,f
node1 is hosting router,registry and other app containers.

Test
For testing HA  i powered off other two nodes and then brought it back after RC started all containers in node1.
When i try to create new builds it fails with above errors in build logs:

As you can see IP address of registry is correct


oc get services
NAME              CLUSTER_IP      EXTERNAL_IP   PORT(S)    SELECTOR                  AGE
docker-registry   172.30.22.132   <none>        5000/TCP   docker-registry=default   16h
haproxy           172.30.94.116   <none>        80/TCP     router=haproxy            13h
kubernetes        172.30.0.1      <none>        443/TCP    <none>                    16h


oc describe service docker-registry

Name:                   docker-registry
Namespace:              default
Labels:                 docker-registry=default
Selector:               docker-registry=default
Type:                   ClusterIP
IP:                     172.30.22.132
Port:                   5000-tcp        5000/TCP
Endpoints:              10.1.0.2:5000
Session Affinity:       None
No events.


oc get no

NAME           LABELS                                STATUS    AGE
10.99.10.191   kubernetes.io/hostname=10.99.10.191   Ready     16h
10.99.10.192   kubernetes.io/hostname=10.99.10.192   Ready     16h
10.99.10.193   kubernetes.io/hostname=10.99.10.193   Ready     16h

I dont understand what triggered this behaviour,i am going to restart node1 to see if that fixes this issue


Thanks for your help


On Sun, Oct 11, 2015 at 3:07 AM, Ben Parees <bparees redhat com> wrote:
can you confirm that 172.30.22.132 is the correct ip for your docker-registry service in the default namespace?

if not you may need to restart your master.


On Sat, Oct 10, 2015 at 4:36 PM, green krypton <greenkrypton93 gmail com> wrote:
builds were all working before  host reboots now builds are failing with error relating to registry.

from build logs:

I1010 19:59:04.416091       1 sti.go:265] Successfully built 172.30.22.132:5000/test/django-example:latest
I1010 19:59:04.488347       1 cleanup.go:23] Removing temporary directory /tmp/sti457404171
I1010 19:59:04.488399       1 fs.go:99] Removing directory '/tmp/sti457404171'
I1010 19:59:04.492804       1 sti.go:149] Using provided push secret for pushing 172.30.22.132:5000/test/django-example:latest image
I1010 19:59:04.492848       1 sti.go:151] Pushing 172.30.22.132:5000/test/django-example:latest image ...
E1010 19:59:28.543880       1 dockerutil.go:73] push for image 172.30.22.132:5000/test/django-example:latest failed, will retry in 5s seconds ...
E1010 20:00:00.601961       1 dockerutil.go:73] push for image 172.30.22.132:5000/test/django-example:latest failed, will retry in 5s seconds ...
E1010 20:00:32.661964       1 dockerutil.go:73] push for image 172.30.22.132:5000/test/django-example:latest failed, will retry in 5s seconds ...
E1010 20:01:01.713838       1 dockerutil.go:73] push for image 172.30.22.132:5000/test/django-example:latest failed, will retry in 5s seconds ...
E1010 20:01:30.766052       1 dockerutil.go:73] push for image 172.30.22.132:5000/test/django-example:latest failed, will retry in 5s seconds ...
E1010 20:01:59.817684       1 dockerutil.go:73] push for image 172.30.22.132:5000/test/django-example:latest failed, will retry in 5s seconds ...
E1010 20:02:28.869729       1 dockerutil.go:73] push for image 172.30.22.132:5000/test/django-example:latest failed, will retry in 5s seconds ...
F1010 20:02:33.870349       1 builder.go:54] Build error: Failed to push image: API error (500): invalid registry endpoint "http://172.30.22.132:5000/v0/". HTTPS attempt: unable to ping registry endpoint https://172.30.22.132:5000/v0/
v2 ping attempt failed with error: Get https://172.30.22.132:5000/v2/: read tcp 172.30.22.132:5000: connection reset by peer
 v1 ping attempt failed with error: Get https://172.30.22.132:5000/v1/_ping: read tcp 172.30.22.132:5000: connection reset by peer. HTTP attempt: unable to ping registry endpoint http://172.30.22.132:5000/v0/
v2 ping attempt failed with error: Get http://172.30.22.132:5000/v2/: read tcp 172.30.22.132:5000: connection reset by peer
 v1 ping attempt failed with error: Get http://172.30.22.132:5000/v1/_ping: read tcp 172.30.22.132:5000: connection reset by peer


Any idea about this 

_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users




--
Ben Parees | OpenShift



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]