Multiuser-OpenShift on OpenShift behind Proxy not starting Workspaces
See original GitHub issueBug
In OpenShift, behind a Proxy Eclipse Che cannot start a workspace. In the Che-Window I can see:
Loading...
Cleaning /plugins dir
Starting Init Plugin Broker
Unified Che Plugin Broker
List of plugins and editors to install
- redhat/java/latest - Java Linting, Intellisense, formatting, refactoring, Maven/Gradle support and more...
- eclipse/che-machine-exec-plugin/0.0.1 - Che Plug-in with che-machine-exec service to provide creation terminal or tasks for Eclipse CHE workspace machines.
- eclipse/che-theia/7.0.0-next - Eclipse Theia, get the latest release each day.
Starting VS Code and Theia plugins processing
Downloading VS Code extension for plugin 'redhat/java/latest'
Starting Che plugins and editor processing
Downloading VS Code extension for plugin 'redhat/java/latest'
All plugins have been successfully processed
MountVolume.SetUp succeeded for volume "jwtproxy-config-volume"
MountVolume.SetUp succeeded for volume "che-workspace-token-kb5v4"
MountVolume.SetUp succeeded for volume "vol28"
MountVolume.SetUp succeeded for volume "vol36"
MountVolume.SetUp succeeded for volume "vol35"
MountVolume.SetUp succeeded for volume "vol139-custom-pv"
MountVolume.SetUp succeeded for volume "che-workspace-token-kb5v4"
pulling image "eclipse/che-jwtproxy:latest"
Container image "maven:3.6.0-jdk-11" already present on machine
Created container
Successfully pulled image "eclipse/che-jwtproxy:latest"
Created container
Started container
pulling image "eclipse/che-machine-exec"
Started container
Successfully pulled image "eclipse/che-machine-exec"
Created container
Started container
pulling image "eclipse/che-theia:7.0.0-next"
Successfully pulled image "eclipse/che-theia:7.0.0-next"
Created container
Started container
pulling image "eclipse/che-remote-plugin-runner-java8:7.0.0-next"
Successfully pulled image "eclipse/che-remote-plugin-runner-java8:7.0.0-next"
Created container
Started container
and then, after some time:
Error: Failed to run the workspace: "Server 'theia' in container 'theia-ide7du' not available."
Additionaly I tried to add java-proxy options to the docker-container by setting the java opts in the environment via openshift:
-Dhttp.proxyHost=a.b.c.d -Dhttp.proxyPort=8080 -Dhttps.proxyHost=a.b.c.d -Dhttps.proxyPort=8080 -Dhttp.nonProxyHosts='localhost|127.0.0.1|*.my-company.de|vm-openshift-02|*.vm-openshift-02|*.vm-openshift-02.my-company.de|172.30.*|10.*'
I can see in the log of the che-pod that the options are used, but it didn’t help.
Che version
7.0.0-rc-5.0-SNAPSHOT
Steps to reproduce
- be behind a proxy 😉
- Install OpenShift (in my case v3.9.0, but I think that is not the problem…)
- Set the environment for the installation
export CHE_WORKSPACE_HTTP__PROXY=http://x.x.x.x:8080/
export CHE_WORKSPACE_HTTPS__PROXY=http://x.x.x.x:8080/
export CHE_WORKSPACE_NO__PROXY=.my-company.de,vm-openshift-02.my-company.de,127.0.0.1,x.y.z.a,localhost,vm-openshift-02,.vm-openshift-02.my-company.de
- install eclipse che with
./deploy_che.sh --multiuser --project=eclipse-che-mu
… - create a new (java) project
Expected behavior
a workspace is running 😉
Runtime
- [1.9] kubernetes
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.1+a0ce1bc657", GitCommit:"a0ce1bc", GitTreeState:"clean", BuildDate:"2018-06-24T01:54:00Z", GoVersion:"go1.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.1+a0ce1bc657", GitCommit:"a0ce1bc", GitTreeState:"clean", BuildDate:"2018-06-24T01:54:00Z", GoVersion:"go1.9", Compiler:"gc", Platform:"linux/amd64"}
- [3.9.0] Openshift
oc v3.9.0+71543b2-33
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://console.vm-openshift-02.team-pb.de:8443
openshift v3.9.0+71543b2-33
kubernetes v1.9.1+a0ce1bc657
- [1.13.1] docker-desktop
Client:
Version: 1.13.1
API version: 1.26
Package version: docker-1.13.1-88.git07f3374.el7.centos.x86_64
Go version: go1.9.4
Git commit: 07f3374/1.13.1
Built: Fri Dec 7 16:13:51 2018
OS/Arch: linux/amd64
Server:
Version: 1.13.1
API version: 1.26 (minimum version 1.12)
Package version: docker-1.13.1-88.git07f3374.el7.centos.x86_64
Go version: go1.9.4
Git commit: 07f3374/1.13.1
Built: Fri Dec 7 16:13:51 2018
OS/Arch: linux/amd64
Experimental: false
Installation method
deploy_che.sh
Environment
CentOS Linux release 7.6.1810 (Core) and a Proxy
There are so many docker container. From which one do you need the log? I looked thrue the logs and I cann not see anything special.
So I think, that the communication between the workspace and the core do not work, because the sender thinks he has to use the proxy … (but it is only a guess…)
Issue Analytics
- State:
- Created 4 years ago
- Comments:36 (10 by maintainers)
Top GitHub Comments
@mshaposhnik Ok, I tested ist and the workspace comes up! So the Error, with the JWTProxy is fixed. Thank You.
https://github.com/eclipse/che-jwtproxy might be an issue.