che: kubernetes "single-host" configuration fails to run new workspaces

I am running a 3 node kubernets cluster running single-host mode with 6.19.0 and it works fine for normal projects. I updated to rc this weekend and found that trying to use the che-7 IDEs did not correctly load the workspace. I see the following error:

Error: Workspace doesn't have a server which matches with URL: http://che.geekcentral.local/?uid=978289

This is the stacktrace from the console:

che.geekcentral.local-1553541995836.log

This is the HAR of the loading the workspace:

che.geekcentral.local.zip

If you need any other logs I can try to extract/clean up the logs from the containers, but I was unsure of what ones to post. I did try the old style projects specificly the “Default Node 8 Stack” and it did work as it did in 6.19.0.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 28 (21 by maintainers)

Most upvoted comments

@bmangaraj : Could you please explain the reason why you would like to deploy in single-host mode? Would the multi-host be convenient for you?

The solution for single-host might get tricky to get, so while we are looking for a solution and get this fixed, I’d recommend a deployment with multi-host mode for the time being.

@bmangaraj at this moment for Che 7 the only one available workaround is to use multi-host https://github.com/eclipse/che/issues/13869#issuecomment-513751078

Thanks for providing HAR of requests. I found in HAR next request that when gets redirected looses path to a server https://gist.github.com/garagatyi/0fb187810cd1c0145ed93af0584d4ad8 Which is probably a bug in our JWT proxy implementation