-
Notifications
You must be signed in to change notification settings - Fork 117
network unreachable #528
Comments
I can't seem to reach that host from my machine -- can you |
i pulled the vagrant image and did a Then i sshd into the machine and did a
the cluster doesn't seem to go down |
Ah, the pre-installed cluster is not created using
The |
stopped the service with
so apparently some http-service is not going down when i stop the service.
and i can login to the gui but i still have the same problem, can't pull images from docker.hub with the gui |
Can you figure out if there is some rogue process still going?
|
destroyed the vagrant, started it again. took down the service with:
started cluster with
|
@csrwng could you help a little with |
Make sure that the firewall allows access to port 8443. Also after cluster up fails, can you try curl'ing that URL and see why it's not accessible ? Is the container (origin) still running? |
hi csrwng , and we have stopped origin and dns service also,but getting same error |
@naveenkumartangallapally try running |
i got below o/p [root@master ~]# netstat -tnlp |
so it looks like you're running openshift (pid 29031) ... which is causing a conflict |
can u help me to fix the issue plz |
kill existing openshift related processes: and then run |
or |
getting same as error as below. |
try systemctl stop atomic-openshift-node as well |
once the cluster is up dashboard is not accessible.might be because node is down? dashboard error: |
Do you mean the web console? That doesn't require the node to be running. But the node is likely running anyway, since 'cluster up' runs the all-in-one which is master+node. |
I would also ask -- just to make sure before much debugging happens, can use you |
My goal is to configure docker-registry, for which there were two containers created with name "docker-registry-1" & "router-1-deploy" when i used quick installation method. However, both the containers were in Error state... One of the blogs i browsed said the containers were in Error state because the oc cluster is not running, which is why i tried to make oc cluster.. Please correct me if I am wrong. Just to add, when i rebooted master and node, i was able to login to web console, but the oc cluster was again in "not running" state. Are docker registry and router creation linked with openshift cluster status??? |
Right, but what reasons are you using for running |
if node is down?what is function of oc cluster? |
If you are trying to achieve a cluster with a router and a registry, one option is to install |
docker and oc are already installed and working fine. But after the oc cluster is up, we are unable to access the dashboard. I dont think we need minishift. Deprecated output of "#oc cluster up" is as follows: OpenShift server started. You are logged in as: To login as administrator: [root@master ~]# oc get pods However, we are unable to access the dashboard with "https://10.0.2.15:8443". Please let me know what are the nodes which are kept in openshift cluster. Is it the master and nodes OR containers created on the node?? |
Ok. Again. please be advised that this codebase is deprecated and not supported. The currently supported method for starting a VM with an OpenShift cluster inside of it is So the cluster is up and running fine inside the VM? If you use |
The cluster is up and running fine inside the VM? Yes, it is...
If you use oc to make actions, they work? Yes.. they do..
Is it forwarding :8443? Yes..
|
Can you hit the console from inside the VM? @jwforres @spadgett have you seen this error from the console before? What does it mean:
|
@naveenkumartangallapally Are you connecting to the web console using a hostname that is not the public hostname? If so, you need add host to the allowed redirect URIs for the web console
|
I thought |
It should do that. I suspect there's something else going in this case. |
i patched up Web console URL: https://10.0.2.15:8443 [root@master ~]# oc patch oauthclient/openshift-web-console -p '{"redirectURIs":["https://10.0.2.15:8443/"]}' |
getting below error while creating docker registry volume:
|
I don't know if this is an issue or not
i pulled the Vagrant image and started it. Was able to login and start a project. But when trying to pull an image from docker hub i get network unrachable.
I have tried setting http_proxy in the vagrant and if i ssh into the machine i can pull and push images with docker inside the openshift-vagrant. But when using the openshift gui i cannot pull images.
i have tried setting the http_proxy in the docker-opts /etc/sysconfig/docker without any luck.
is this a known issue?
The text was updated successfully, but these errors were encountered: