No route to host is usually a configuration issue with openshift SDN - most commonly on things like AWS it's that the firewall doesn't allow traffic on the SDN port (which I think is 4789) to pass between nodes.
On Thu, May 19, 2016 at 11:01 AM, holo holo <[email protected]> wrote: > one more log connected with same thing: > > > E0519 11:00:09.099712 2098 pod_workers.go:138] Error syncing pod > 5d3c48a1-1dd2-11e6-a164-525400c36a07, skipping: failed to "StartContainer" > for "testapp4" with ErrImagePull: "API error (500): Get > http://172.30.236.174:5000/v2/: dial tcp 172.30.236.174:5000: getsockopt: no > route to host\n" > > > //robert > > On Thu, May 19, 2016 at 4:55 PM, holo holo <[email protected]> wrote: >> >> Hello all. >> >> I configured openshift and everything is working properly on host where >> docker-register is started. When i added new node and i try to deploy >> containers on it i have such error in logs: >> >> E0519 10:51:38.574152 2135 pod_workers.go:138] Error syncing pod >> 083b958e-1dc0-11e6-8ca2-525400c36a07, skipping: failed to "StartContainer" >> for "testapp4" with ImagePullBackOff: "Back-off pulling image >> \"172.30.236.174:5000/test/testapp4@sha256:64c3dc4cb983986a1dd5a7979f03f449b089f4baaf979b67363a92aac43e49cd\"" >> >> I'm guessing problem is with it that new node not "see" docker-registry >> address 172.30.236.174 which is deployed on other node. Should i do >> something more with new node (i just started openshift with node config)? >> >> Best regards >> Robert > > > > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
