-
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
Cannot delete a workspace in PREPARING phase #4173
Comments
I have observed this issue as well. |
Deleting workspaces in any phase but RUNNING or STOPPED is very difficult. I reckon we should rather disable the "Delete" item in the menu if the workspace is neither running nor stopped. |
Thanks @csweichel for the insight! Agree, adding the following to the issue description. Let me know if the second option below sounds inefficient. 🏓 We could either a) disable the workspace delete dropdown option or b) remove the entry from the user interface and handle all the background tasks needed to gracefully delete a workspace. |
Previously a workspace could be deleted in any state, what changed? I assumed that (previously) the workspace was removed from the list until all the background tasks for deleting the workspace had been completed. I use to rely on this functionality, it was useful. |
/schedule |
Thank you for pointing this out. Except for "in preparation" workspaces in other phases can be stopped (which is what we're doing, actually). It would seem that the deletion doesn't happen reliably afterwards though, i.e. the workspace is stopped but not necessarily deleted). |
This seems to be related: https://community.gitpod.io/t/unable-to-delete-workspace/4956 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bug description
Users cannot delete workspaces in
PREPARING
phase.Steps to reproduce
/workspaces
)PREPARING
phase.Expected behavior
Workspace should be deleted.
According a reference to the comment in #4173 (comment).
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: