Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot see list of workspaces after clicking 'Return to dashboard' #21950

Closed
Tracked by #21941
dkwon17 opened this issue Jan 23, 2023 · 1 comment · Fixed by eclipse-che/che-dashboard#729
Closed
Tracked by #21941
Assignees
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system. sprint/current status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording
Milestone

Comments

@dkwon17
Copy link
Contributor

dkwon17 commented Jan 23, 2023

Describe the bug

After reaching the maximum # of running workspaces, if I try to start another workspace, I get this message:

You can only have 2 running workspaces at a time.

[Return to dashboard]

If I click [Return to dashboard], I am brought to the dashboard, but, the list of workspaces are not available on the left-hand side:

Screen.Recording.2023-01-23.at.6.46.42.PM.mov

The navbar also seems to be missing.

The workaround is to refresh the page.

Che version

next (development version)

Steps to reproduce

  1. Reach the maximum # of running workspaces, and then try to start another workspace.
  2. On the error message, click Return to dashboard

Expected behavior

The list of recent workspaces should be available on the left hand side:
image

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

macOS

Eclipse Che Logs

No response

Additional context

No response

@dkwon17 dkwon17 added the kind/bug Outline of a bug - must adhere to the bug report template. label Jan 23, 2023
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jan 23, 2023
@ibuziuk ibuziuk added severity/P1 Has a major impact to usage or development of the system. area/dashboard sprint/next and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jan 24, 2023
@ibuziuk ibuziuk mentioned this issue Feb 15, 2023
56 tasks
@l0rd l0rd added new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording labels Mar 2, 2023
@l0rd l0rd added this to the 7.62 milestone Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard kind/bug Outline of a bug - must adhere to the bug report template. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system. sprint/current status/release-notes-review-needed Issues that needs to be reviewed by the doc team for the Release Notes wording
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants