-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Enable single running workspace restriction for DevWorkspaces started from UD #21032
Enable single running workspace restriction for DevWorkspaces started from UD #21032
Comments
looks like it is possible to start multiple workspace from getting-started on the dogfooding instance :/ reopening |
funny enough I can not reproduce the problem locally against 'main' 🤷 |
Can not reproduce it anymore on the dogfooding also. Closing |
I can reproduce the problem locally against main |
Should be fixed in devspaces dashboard 3.0-16 in downstream https://quay.io/repository/devspaces/dashboard-rhel8?tab=tags&tag=3.0-16 |
Describe the bug
It is possible to start multiple devworkspaces from UD. The second and subsequent would fail on some clusters due to RWO limitation.limitations
Che version
7.41@latest
Steps to reproduce
start a devworkspace from UD when there is already one running.
Expected behavior
It should be possible to have only one running workspace by default
Runtime
OpenShift
Screenshots
what is more workspace startup is failing with the Unknown Error:
Installation method
OperatorHub
Environment
Amazon
Eclipse Che Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: