Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Single host mode: error starting workspace

See original GitHub issue

Che version

7.0 And 7.2 snapshot (using latest che-server image)

Steps to reproduce

install with helm
create workspace and project

Expected behavior

should see IDE

Runtime

kubernetes (include output of kubectl version)

[root@k8s_lab ~]# kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.2", GitCommit:"f6278300bebbb750328ac16ee6dd3aa7d3549568", GitTreeState:"clean", BuildDate:"2019-08-05T09:23:26Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.2", GitCommit:"f6278300bebbb750328ac16ee6dd3aa7d3549568", GitTreeState:"clean", BuildDate:"2019-08-05T09:15:22Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}

Installation method

helm install using single-host mode

Environment

Windows + VMWare VM

Additional context

helm install che 7.0 in notebook in wmare workstation VM on windows 10

global:
  multiuser: true
  ingressDomain: mychedomain
  serverStrategy: single-host

workspace started successful

[root@k8s_lab che]# kubectl get pods --all-namespaces
NAMESPACE       NAME                                                       READY   STATUS    RESTARTS   AGE
che-workspace   workspace5km0dnswcmkbo85i.che-jwtproxy-689c4fd7b8-gqlbf    1/1     Running   0          3d15h
che-workspace   workspace5km0dnswcmkbo85i.maven-74c5c7d78c-qt9tf           4/4     Running   0          3d15h
default         che-545f75d787-8v5bm                                       1/1     Running   0          3d16h
default         devfile-registry-5dd598f5b-ccn2h                           1/1     Running   0          3d16h
default         keycloak-75697bcf67-r6z95                                  1/1     Running   0          3d16h
default         myingress-nginx-ingress-controller-84bd985c9d-n7mvn        1/1     Running   0          6d14h
default         myingress-nginx-ingress-default-backend-5d8fdb67ff-zm2pw   1/1     Running   2          12d
default         plugin-registry-77bd486f58-7vjlx                           1/1     Running   0          3d16h
default         postgres-6cd55dcd98-cd26s                                  1/1     Running   0          3d16h
kube-system     calico-kube-controllers-8578c8767f-45klr                   1/1     Running   2          17d
kube-system     calico-node-6sz6k                                          1/1     Running   2          17d
kube-system     coredns-855ddf9dd4-zh4w5                                   1/1     Running   0          4d23h
kube-system     tiller-deploy-5cd86d8fcd-vzt4n                             1/1     Running   2          17d

ingress also ready

[root@k8s_lab che]#  kubectl get ingress --all-namespaces
NAMESPACE       NAME               HOSTS                                  ADDRESS   PORTS   AGE
che-workspace   ingress4lk9vy3a    mychedomain                                      80      3d15h
che-workspace   ingress5pktpa1j    mychedomain                                      80      3d15h
che-workspace   ingressckahk4fo    mychedomain                                      80      3d15h
che-workspace   ingresspdmmks94    mychedomain                                      80      3d15h
che-workspace   ingressto3g3nvb    mychedomain                                      80      3d15h
che-workspace   ingressxxsm05n8    mychedomain                                      80      3d15h
default         che-ingress        mychedomain                                      80      3d16h
default         devfile-registry   devfile-registry-default.mychedomain             80      3d16h
default         keycloak-ingress   mychedomain                                      80      3d16h
default         plugin-registry    plugin-registry-default.mychedomain              80      3d16h

workspace related server also ok

but browser show error:

Error: Workspace doesn't have a server which matches with URL: http://mychedomain/?uid=568464

Issue Analytics

State:
Created 4 years ago
Comments:14 (9 by maintainers)

Top GitHub Comments

1reaction

leader-uscommented, Sep 11, 2019

Thanks for help . I tried pull latest nightly image and restarted che-server pod. and now single host mode successfully started

but there are some error msg in browser .

1reaction

skabashnyukcommented, Sep 10, 2019

@leader-us ok. Could you please next time use the original template of the bug report. Thanks.

Top Results From Across the Web

Troubleshoot a WorkSpace stuck in starting, rebooting, or ...

Connect to the WorkSpace using RDP. Open the Start menu, and then navigate to Control Panel > Network and Internet > Network and...

Catalyst 4500 Series Switch Software Configuration Guide ...

The 802.1X port's host mode determines whether more than one client can be authenticated on the port and how authentication is enforced.

Chapter 4. Known issues Red Hat CodeReady Workspaces 2.11 ...

When using the single-host strategy for workspace exposure, attempting to clone a ... The crwctl binaries do not run on IBM Z and...

docker run - Docker Documentation

Cgroup namespace to use (host|private) 'host': Run the container in the Docker ... as configured by the default-cgroupns-mode option on the daemon (default)....

Installing the Workspace ONE Access Connector - VMware Docs

Regardless of the type of installation you choose, you can run the ... Workspace ONE Access Connector 21.08 does not support integration ......