Error: Failed to get the workspace: "Unknown error"

[skabashnyuk]

Describe the bug

I was not able to load my go based workspace.

Che version

• latest

Steps to reproduce

Unknown.
I just create a go based workspace and try to start it.

Expected behavior

The workspace should load correctly.

Runtime

• Openshift (include output of oc version)

Screenshots

Installation method

• chectl
  chectl server:start --platform=crc --installer=operator --os-oauth --tls --self-signed-cert

Environment

• macOS

Additional context

#14931

[ibuziuk]

confirm having this kind of issue on crc

[l0rd]

@skabashnyuk that's nightly right? cc @olexii4

[skabashnyuk]

@skabashnyuk that's nightly right?

yes

[olexii4]

@l0rd
It is a workspace-loader error. It can depend on self-signed-cert. I didn't see this error.

We have an issue about self-signed-cert errors
Dashboard messages should be more accurate when self-signed cert issue happens, but it is not cover a possible error in the workspace-loader.

@akurinnoy What do you think about this workspace-loader error? Do you have a similar problem with your macOS?

[skabashnyuk]

Reproduced for me on new crc cluster with a first starting workspace.

Failed request

curl 'https://che-che.apps-crc.testing/api/workspace/workspaceyht1t42gstrzts92' -H 'Connection: keep-alive' -H 'Pragma: no-cache' -H 'Cache-Control: no-cache' -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.106 Safari/537.36' -H 'Sec-Fetch-Dest: empty' -H 'Accept: */*' -H 'Sec-Fetch-Site: same-origin' -H 'Sec-Fetch-Mode: cors' -H 'Referer: https://che-che.apps-crc.testing/workspace-loader/skabashn/golang-zwj7o?uid=211051' -H 'Accept-Language: uk-UA,uk;q=0.9,ru-UA;q=0.8,ru;q=0.7,en-US;q=0.6,en;q=0.5' -H 'Cookie: 0f443a2a27de429b7964dbc8f3c18ef4=1298ba066292e063f01a89a71b711f9a' --compressed

[skabashnyuk]

[sleshchenko]

@skabashnyuk Thanks for sharing details...
Seems that token is expired, the token is refreshed, the request is made with the expired token, the token is refreshed.

Not sure how workspace loader use keycloak script, maybe there is way to ask keycloak to make sure that token is valid before doing request. @akurinnoy Do you remember that area?

I wonder if you face the same issue during switching tabs in Dashboard.

[akurinnoy]

@sleshchenko yes, workspace loader asks keycloak to update token before doing any requests, otherwise it redirects to login. Same as @skabashnyuk I faced this issue on new CRC cluster while starting the first workspace for the first time and couldn't reproduce it more.

[Katka92]

I can see that issue too from time to time on a nightly Che deployed on OpenShift cluster. I'm using chectl for installation, also using tls and self-signed certs.

[akurinnoy]

@skabashnyuk I'm not able to reproduce this bug anymore. Could you please confirm or deny same on your side?

[skabashnyuk]

No longer reproduced.