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.

Sign up for GitHub

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

Jump to bottom

Don't allow to start workspace if user already reached runtime number limit #15716

Open
maxandersen opened this issue Jan 16, 2020 · 2 comments
Open

Don't allow to start workspace if user already reached runtime number limit #15716

maxandersen opened this issue Jan 16, 2020 · 2 comments
Labels
area/dashboard kind/enhancement A feature request - must adhere to the feature request template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@maxandersen
Copy link

Is your enhancement related to a problem? Please describe.

when I create a second workspace on che.openshift.io it only errors after changing screens, loaded a bit and then it errors that I have already one workspace open.

Describe the solution you'd like

On the create workspace screen where the UI already knows I have 1 workspace running, block or at least warn me from creating a workspace if my limit only allows for 1 workspace.

The current mechanism is very tedious to work with.
@maxandersen maxandersen added the kind/enhancement A feature request - must adhere to the feature request template. label Jan 16, 2020
@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 16, 2020
@tsmaeder tsmaeder added area/che-server severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jan 17, 2020
@che-bot
Copy link
Contributor

che-bot commented Jul 27, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 27, 2020
@che-bot che-bot closed this as completed Aug 21, 2020
@sleshchenko sleshchenko reopened this Aug 25, 2020
@che-bot che-bot closed this as completed Sep 9, 2020
@sleshchenko sleshchenko added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 10, 2020
@sleshchenko sleshchenko reopened this Sep 10, 2020
@sleshchenko sleshchenko changed the title open workspace when already one running should error sooner. Don't allow to start workspace if user already reached runtime number limit Oct 1, 2020
@ibuziuk
Copy link
Member

ibuziuk commented Feb 2, 2022

Related issue for DevWorkspace - #21032

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/dashboard kind/enhancement A feature request - must adhere to the feature request template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@maxandersen @nickboldt @ibuziuk @slemeur @sleshchenko @tsmaeder @che-bot