Error Route and path matches, but all pods are down at workspace startup

[l0rd]

Describe the bug

Che version

7.75@latest

Steps to reproduce

I am not able to reproduce this systematically. It happens from time to time on dogfooding instance starting a workspace. Clicking "retry" makes it work.

Environment

Dogfooding instance

[l0rd]

@amisevsk @ibuziuk @tolusha do you have any clue why this can happen?

[tolusha]

What about events?

[amisevsk]

Are there any issues with the Che Gateway deployment (logs, restarting pods, etc.)?

I think that's the HTML for the "Application not running" page OpenShift shows when the route doesn't find any deployments.

[l0rd]

Could it be that's VS Code that's ready before the gateway? I don't have logs / events but I will get them if I am able to reproduce this problem.

[amisevsk]

It's strange because the final readiness check for "workspace is ready" is to make a request on the main url, which would make that unlikely since the gateway would have to go down between the readiness request and the redirect from dashboard.

I could also be a route issue (e.g. return 404, then the unavailable page)

[dkwon17]

This issue came from a failed server-config request, which is made by the dashboard here. I did create this PR: eclipse-che/che-dashboard#1039 but it doesn't deal with the root problem.

@amisevsk is correct, the error message is the HTML page for the "Application not running" page OpenShift shows when the route doesn't find any deployments.

This particular issue is rare and intermittent, and I think it can potentially happen when making any request to che-gateway.

For example, today I got the same error when I was accessing the dashboard, when the dashboard was getting resources:

I didn't see anything suspicious in the gateway logs, or events.

We could try enabling ingress access logs and see if that might provide more details

[dkwon17]

I believe we can close this issue thanks to the merge of eclipse-che/che-dashboard#1039,

If I can reproduce the issue in #22641 (comment) again, I will create a new issue