We made it.
The following things had to be done after the upgrade:
-install origin-node package (with its dependencies like docker etc.) on the
master host and get the origin-node service running
-add a DNS entry for the name of the new node on the master host
However, we could have saved ourselves nearly 3 days of troubleshooting if it
were documented anywhere that that with the upgrade to origin 1.1 you need to
install the origin-node package on the master host. Using Openshift without an
enterprise contract has been a terrible experience for us.
Regards
v
Am 2016-04-07 um 16:08 schrieb v:
Hello
we saw an interesting message on "openshift ex diagnostics" and installed the
origin-node package on our master (which used to be only a master without the origin-node
package before the upgrade to 1.1.4).
When we use "oc new-app" with an image from our registry we now get:
error: can't look up Docker image "172.30.35.180:5000/abc/xyz:latest
<http://172.30.35.180:5000/abc/xyz:latest>": Internal error occurred: Get
https://172.30.35.180:5000/v2/: dial tcp 172.30.35.180:5000 <http://172.30.35.180:5000>: *no
route to host*
When we use "telnet 172.30.35.180 5000" from our master we also get "*no route to
host*"! It seems like we are closing in on the issue and we only need to get the SDN working
on our master.
However, when troubleshooting the SDN we did not find any obvious errors. Do we
need to add some iptables rules to our master to allow him to join the SDN? Any
help would be highly appreciated!
Best Regards
v
Am 2016-04-05 um 18:04 schrieb v:
Am 2016-04-05 um 17:53 schrieb Ben Parees:
On Tue, Apr 5, 2016 at 11:44 AM, v <[email protected] <mailto:[email protected]>>
wrote:
Hello
we have upgraded to OS 1.1.4 and we are getting the following error message
when using oc new-app to start an app which uses an image from our registry:
oc new-app 172.30.35.180:5000/abc/xyz:latest
<http://172.30.35.180:5000/abc/xyz:latest>
error: can't look up Docker image "172.30.35.180:5000/abc/xyz:latest
<http://172.30.35.180:5000/abc/xyz:latest>": Internal error occurred: Get
https://172.30.35.180:5000/v2/: dial tcp 172.30.35.180:5000 <http://172.30.35.180:5000>:
network is unreachable
error: no match for "172.30.35.180:5000/abc/xyz:latest
<http://172.30.35.180:5000/abc/xyz:latest>"
Howerver, the following things work:
-oc new-app with an image from docker.io <http://docker.io>
-pushing to the registry (docker login, docker push)
-telnet 172.30.35.180 5000 works from all nodes
This is a very weird error because telnet works. And the error only started
appearing after the upgrade. Any help would be highly appreciated.
do you have any http_proxy/https_proxy env variables configured?
Regards
v
_______________________________________________
users mailing list
[email protected] <mailto:[email protected]>
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
--
Ben Parees | OpenShift
Hello,
We thought of that possibility too. But we don't use a proxy:
ps -eF | grep docker
root 6503 1 10 1767802 153628 1 13:15 ? 00:29:32 /usr/bin/docker
daemon --insecure-registry=172.30.0.0/16 --selinux-enabled --log-level=warn
--storage-driver devicemapper --storage-opt dm.fs=xfs --storage-opt
dm.thinpooldev=/dev/mapper/docker--vg-docker--pool --storage-opt
dm.use_deferred_removal=true -b=lbr0 --mtu=1450
Is there any other place where http_proxy/https_proxy env variables could be
configured other than in the global docker daemon settings? Or anything else
which could cause that?
Regards,
v
_______________________________________________
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
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users
