[CRW-2899] "504 Gateway Time-out" after workspace went offline, and it wasn't clear how to restore workspace - Red Hat Issue Tracker

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Done
Affects Version/s: 3.0.0.GA
Fix Version/s: 3.1.0.GA
Component/s: controller: dashboard, factory/dashboard, ts-workspace-client
Labels:
- regression

Blocked:
False
Blocked Reason:
None
Ready:
False
Release Note Text:

Hide
= *503 Service Unavailable* or *504 Gateway Time-out* errors

Currently, you might encounter a *503 Service Unavailable* or *504 Gateway Time-out* error message after refreshing the page of a stopped workspace.

Workaround: Restart the workspace from the dashboard.

Show
= *503 Service Unavailable* or *504 Gateway Time-out* errors Currently, you might encounter a *503 Service Unavailable* or *504 Gateway Time-out* error message after refreshing the page of a stopped workspace. Workaround: Restart the workspace from the dashboard.
Workaround:

Workaround Exists
Workaround Description:
Hide

(Rephrased in case we have to use this as a KI entry...

For a given workspace like https://devspaces-openshift-workspaces.apps.yourclusterhere/dashboard/#/ide/usernamehere-devspaces/workspacenamehere ...

Open a browser tab to https://devspaces-openshift-workspaces.apps.yourclusterhere/dashboard/

Locate the workspace in the left panel, or from the Workspaces page

Note: if workspace is created via factory, generated name may differ from the Git project name or devfile settings.

Restart the workspace
Show
(Rephrased in case we have to use this as a KI entry... For a given workspace like https://devspaces-openshift-workspaces.apps.yourclusterhere/dashboard/#/ide/usernamehere-devspaces/workspacenamehere ... Open a browser tab to https://devspaces-openshift-workspaces.apps.yourclusterhere/dashboard/ Locate the workspace in the left panel, or from the Workspaces page Note: if workspace is created via factory, generated name may differ from the Git project name or devfile settings. Restart the workspace
Release Note Status:
Documented as Known Issue