Skip to main content
Server Fault

Return to Question

added 83 characters in body; edited title
Source Link
user14805338
user14805338
  • 11
  • 2

OpenOpen Open shift dockerinternal registry lost connection with the cluster

As a result getting image pull error while submitting the deployment to the kube API. Even the docker registry pod IP is in connection but VIRTUAL IP of docker registry lost connection with the cluster.

Observed these logs in server. Error response from daemon: Get http://VIRTUAL IP:5000/v1/users/: dial tcp 172.30.11.76:5000: connect: no route to hostObserved these logs in server. Error response from daemon: Get http://VIRTUAL IP:5000/v1/users/: dial tcp VIRTUAL IP:5000: connect: no route to host

DockerOpenshift internal registry lies in different project that is default. Previously, it was connected properly, the diconnectiondisconnection happened suddenly.

Epitome of the issue: Docker registry virtual IP lost connection with the entire openshift cluster. So, is there a possible way that we can re-establish the connection between the docker registry'sOpen shift internal registry 'ss virtual IP and openshift cluster?

How can re-establish the connection the internal registry and the rest of the cluster??

OpenOpen shift docker registry lost connection with the cluster

As a result getting image pull error while submitting the deployment to the kube API. Even the docker registry pod IP is in connection but VIRTUAL IP of docker registry lost connection with the cluster.

Observed these logs in server. Error response from daemon: Get http://VIRTUAL IP:5000/v1/users/: dial tcp 172.30.11.76:5000: connect: no route to host

Docker registry lies in different project that is default. Previously, it was connected properly, the diconnection happened suddenly.

Epitome of the issue: Docker registry virtual IP lost connection with the entire openshift cluster. So, is there a possible way that we can re-establish the connection between the docker registry's virtual IP and openshift cluster?

How can re-establish the connection the internal registry and the rest of the cluster??

Open shift internal registry lost connection with the cluster

As a result getting image pull error while submitting the deployment to the kube API. Even the docker registry pod IP is in connection but VIRTUAL IP of docker registry lost connection with the cluster.

Observed these logs in server. Error response from daemon: Get http://VIRTUAL IP:5000/v1/users/: dial tcp VIRTUAL IP:5000: connect: no route to host

Openshift internal registry lies in different project that is default. Previously, it was connected properly, the disconnection happened suddenly.

Epitome of the issue: Docker registry virtual IP lost connection with the entire openshift cluster. So, is there a possible way that we can re-establish the connection between the Open shift internal registry 'ss virtual IP and openshift cluster?

How can re-establish the connection the internal registry and the rest of the cluster??

Source Link
user14805338
user14805338
  • 11
  • 2

OpenOpen shift docker registry lost connection with the cluster

As a result getting image pull error while submitting the deployment to the kube API. Even the docker registry pod IP is in connection but VIRTUAL IP of docker registry lost connection with the cluster.

Observed these logs in server. Error response from daemon: Get http://VIRTUAL IP:5000/v1/users/: dial tcp 172.30.11.76:5000: connect: no route to host

Docker registry lies in different project that is default. Previously, it was connected properly, the diconnection happened suddenly.

Epitome of the issue: Docker registry virtual IP lost connection with the entire openshift cluster. So, is there a possible way that we can re-establish the connection between the docker registry's virtual IP and openshift cluster?

How can re-establish the connection the internal registry and the rest of the cluster??