Can't get CHE running on Rancher K8S Cluster

Summary

I try to setup Eclipse CHE on a Rancher Kubernetes Cluster. I used for this the helm chart with some modifications. It’s all starting and i can login in dashboard, but I can’t create any new workspaces. I tried some tipps from older issues but nothing helped. How can I solve this?

Errorlog from “CHE” Container: 2021-01-25 19:14:21,228[aceSharedPool-1] [ERROR] [o.e.c.c.t.TracingInterceptor 63] - Plugins installation process timed out org.eclipse.che.api.workspace.server.spi.InfrastructureException: Plugins installation process timed out at org.eclipse.che.workspace.infrastructure.kubernetes.wsplugins.brokerphases.WaitBrokerResult.execute(WaitBrokerResult.java:75) at org.eclipse.che.workspace.infrastructure.kubernetes.wsplugins.brokerphases.DeployBroker.execute(DeployBroker.java:129) at org.eclipse.che.workspace.infrastructure.kubernetes.wsplugins.brokerphases.PrepareStorage.execute(PrepareStorage.java:76) at org.eclipse.che.workspace.infrastructure.kubernetes.wsplugins.brokerphases.ListenBrokerEvents.execute(ListenBrokerEvents.java:63) at org.eclipse.che.workspace.infrastructure.kubernetes.wsplugins.PluginBrokerManager.getTooling(PluginBrokerManager.java:129) at org.eclipse.che.core.tracing.TracingInterceptor.invoke(TracingInterceptor.java:61) at org.eclipse.che.workspace.infrastructure.kubernetes.wsplugins.SidecarToolingProvisioner.provision(SidecarToolingProvisioner.java:90) at org.eclipse.che.core.tracing.TracingInterceptor.invoke(TracingInterceptor.java:61) at org.eclipse.che.workspace.infrastructure.kubernetes.KubernetesInternalRuntime.provisionWorkspace(KubernetesInternalRuntime.java:288) at org.eclipse.che.workspace.infrastructure.kubernetes.KubernetesInternalRuntime.internalStart(KubernetesInternalRuntime.java:204) at org.eclipse.che.api.workspace.server.spi.InternalRuntime.start(InternalRuntime.java:141) at org.eclipse.che.core.tracing.TracingInterceptor.invoke(TracingInterceptor.java:61) at org.eclipse.che.api.workspace.server.WorkspaceRuntimes$StartRuntimeTask.run(WorkspaceRuntimes.java:969) at org.eclipse.che.commons.lang.concurrent.CopyThreadLocalRunnable.run(CopyThreadLocalRunnable.java:38) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(Unknown Source) at io.opentracing.contrib.concurrent.TracedRunnable.run(TracedRunnable.java:30) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) 2021-01-25 19:14:21,239[aceSharedPool-1] [INFO ] [o.e.c.a.w.s.WorkspaceRuntimes 995] - Workspace 'admin:dotnet-oy8fw' with id 'workspacexde6yczug65tvm69' start failed 2021-01-25 19:14:22,303[ajor-endpoint-0] [ERROR] [.e.c.a.c.j.c.RequestDispatcher 62] - No corresponding to method 'unsubscribe' handler is registered 2021-01-25 19:25:27,088[aceSharedPool-2] [INFO ] [o.e.c.a.w.s.WorkspaceRuntimes 1106] - Runtime 'workspace9edw06uph3i0cj9h:default:b07e3a58-ed50-4a6e-be17-fcf49ff8b242' is stopping abnormally. Reason: Workspace is not started in time. Trying interrupt runtime start

Relevant information

• cheWorkspaceHttpProxy: “http://172.25.28.25:8080”
• cheWorkspaceHttpsProxy: “http://172.25.28.25:8080”
• cheWorkspaceNoProxy: “10.0.0.0/8”
• multiuser=true
• serverStrategy: multi-host
• singleHostExposure: native
• tls=enabled with own secret

[gorshkov-leonid]

@tolusha It seems I’ve found a bug. All works if a certificate has \n at the end, But in my case, I was using a certificate that ends with “…END CERTIFICATE-----<EOF>”

[gorshkov-leonid]

@tolusha maybe you know something about the possible reason?