minishift: Che fails on version 1.4.1
Che has a service named che-host that has a route configured. When the service is trying to reach itself through the internal names it fails, public route works fine. When I ssh into the pod and try to curl to http://che-host it fails after a long wait where as http://localhost and with internal ip address works fine.
Also when I enable the logs I see lines like follow for every pod.
1610 docker_sandbox.go:263] Couldn't find network status for eclipse-che/che-3-deploy through plugin: invalid network status for
We also did a minishift ssh and compared /etc/resolv.conf with 1.3.1 and 1.4.1 only has a single nameserver entry where as 1.3.1 also includes and entry for search.
@amisevsk Anything else I am missing?
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 17 (9 by maintainers)
@gorkem can you try out it with minishift 1.5.0 without any workaround and let us know if it still fail because here we are using 3.6.0 as default openshift version.
I’ve managed to narrow this down somewhat.
Running minishift 1.4.1 and Openshift version
I am able to reproduce the issue. Running minishift 1.4.1 and OpenShift v1.5.1 it does not occur.
However, the issue is actually that pods cannot resolve their own service or service’s clusterIP. Starting a second pod, I can curl che-host without issue, but from within che host I cannot. There are no real networking issues except that pods cannot access their own services – localhost and external work fine.
After a bit of digging, I came across this section of kubernetes documentation that seems related.
@gbraad Is there a setting that has changed between 1.5.1 and 3.6? I don’t see this issue on OpenShift Online, running