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

Stop an already running workspace when we create and start a second workspace #18291

Closed
chopraaakash91 opened this issue Nov 5, 2020 · 6 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/P1 Has a major impact to usage or development of the system.

Comments

@chopraaakash91
Copy link

Hi team , if 1 workspace is already running, and i try to create and start 2nd workspace, it gives error saying that you can not start more than 1 workspace. Is it possible that when i start second workspace, first one should get automatically stopped. I don't want to enable this - https://www.eclipse.org/che/docs/che-7/installation-guide/running-more-than-one-workspace-at-a-time/

is there a way to achieve this ?

@chopraaakash91 chopraaakash91 added the kind/enhancement A feature request - must adhere to the feature request template. label Nov 5, 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 Nov 5, 2020
@l0rd
Copy link
Contributor

l0rd commented Nov 5, 2020

It makes sense to ask the user if he wants to stop the active workspace and start a new one of if he wants to abort.

@themr0c themr0c added area/dashboard team/controller severity/P1 Has a major impact to 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 Nov 9, 2020
@che-bot
Copy link
Contributor

che-bot commented May 18, 2021

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 May 18, 2021
@che-bot che-bot closed this as completed Jun 7, 2021
@sleshchenko sleshchenko reopened this Jun 11, 2021
@sleshchenko sleshchenko removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 11, 2021
@che-bot
Copy link
Contributor

che-bot commented Dec 13, 2021

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 Dec 13, 2021
@l0rd
Copy link
Contributor

l0rd commented Dec 13, 2021

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 13, 2021
@che-bot
Copy link
Contributor

che-bot commented Jun 11, 2022

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 Jun 11, 2022
@l0rd l0rd 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 Jun 13, 2022
@akurinnoy
Copy link
Contributor

I'm closing the issue because it was resolved in eclipse-che/che-dashboard#607 and then improved in eclipse-che/che-dashboard#618 and eclipse-che/che-dashboard#620.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

6 participants