Dashboard doesn't reconnect to a WebSocket endpoint if the previous connection failed

[sleshchenko]

Description

Dashboard doesn't reconnect to a WebSocket endpoint if the previous connection failed. As result Dashboard doesn't receive any event about workspaces status changes.

Reproduction Steps

It happens on all infrastructures Docker, OpenShift, Kubernetes. But it can be reproduced stably only on Kubernetes infrastructure, on other, it happens quite rarely.

I suppose it happens because of nginx ingress controller. K8s infra adds new ingress for each workspace server and nginx controller restarts itself when new ingress rule is added. So, there is an ability to configure ingress controller for created workspaces ingresses. So only Dashboard should be fixed, and WebSocket connections can be made stable with another ingress controller (I suppose traefik ingress controller can be used for such purposes)

It can be reproduced in the following way:

1. Deploy Che on Kubernetes.
2. Create workspace.
3. Open Developer Console and watch WebSocket connections.
4. Run workspace in IDE.
5. Check a WebSocket connection to wsmaster from the dashboard.
   Actual: Dashboard websocket connection is closed, as result Dashboard shows that workspace is STARTING when it is STARTED.
   Expected: Dashboard websocket connection is pending, Dashboard receives events that workspace is started and updates Workspace Status Icon.

More see screencast

OS and version:

Diagnostics: