che: Failed to start Kubernetes runtime of workspace. Cause: Server theia in container theia-ide not available.

k8s 1.17.3 on baremetal centos7. Cluster is being used for testing purposes and all works fine (so far).

Che has been set up with chectl using the operator method. Tried this with versions 7.9.2, 7.10.0 and nightly with the same effect.

Setup has been done with FQDN and --tls --self-signed-cert and a previously imported root CA as described in the docs.

When trying to create a workspace the che container reports:

2020-03-25 11:39:39,208[aceSharedPool-1]  [WARN ] [.i.k.KubernetesInternalRuntime 263]  - Failed to start Kubernetes runtime of workspace workspace7obhq7tk4sa8q9xq. Cause: Server 'theia' in container 'theia-idek90' not available.
2020-03-25 11:39:40,880[aceSharedPool-1]  [INFO ] [o.e.c.a.w.s.WorkspaceRuntimes 944]   - Workspace 'admin:java-maven-xvnj0' with id 'workspace7obhq7tk4sa8q9xq' start failed

the theia container has some warning and errors, only the errors here

2020-03-25 11:41:41.455 root ERROR Failed to load plugin dependencies from '/plugins/installed.json' path Params: Error: ENOTDIR: not a directory, open '/plugins/installed.json/package.json'
2020-03-25 11:41:41.506 root ERROR Failed to load plugin dependencies from '/plugins/sidecars' path Params: Error: ENOENT: no such file or directory, open '/plugins/sidecars/package.json'

but finally reports:

2020-03-25 11:42:12.524 root INFO Deploy plugins list took: 31206.6 ms

There is not intresting to be found in the event-log.

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 49 (21 by maintainers)

Most upvoted comments

@sleshchenko

when I try this URL directly (of course fetched the acutal one after restart) I get a 404.

when I try https://che-che.test.yars.lemarit.com/_app/loader.html?redirectUrl=https://server3cj87zqm-jwtproxy-webviews.test.yars.lemarit.com/&workspaceId=workspacesh9n48gcsw0jwrzb&token=eyJhbGciOiJSUzI1NiIsImtpbmQiOiJtYWNoaW5lX3Rva2VuIiwia2lkIjoid29ya3NwYWNlc2g5bjQ4Z2NzdzBqd3J6YiJ9

I get Error: Failed to authenticate: "Unknown error"

I checked the events and all logs from the pods in the che namespace but found nothing related.

SockenSalat on Apr 8, 2020