-
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
Please force-stop workspace instances that are "stuck" in a bad state #5016
Comments
Note: I've tried force-stopping my own stuck workspace instance ( Before my intervention, the instance looked like this in Gitpod's DB:
I then did this in order to force-stop it:
This successfully returned my workspace back to "stopped" in my Gitpod dashboard, however when I tried to start it again, it said:
I suppose that's because there was never a backup made for this workspace. I wonder, what is the correct fix here? Delete the instance stuck in |
On a side note, there are several workspace instances stuck in similar "temporary" states, sometimes for quite a long time: For > 24h
for > 1 month
I suppose these should all get forcefully stopped at some point. |
Most of them are prebuilds. One that wasn't a prebuild had lots of |
We should have ws-manager-bridge correct such instances as part of its regular reconciliation loop. |
/schedule |
Is this a dupe -> #4955 |
/assign @mrsimonemms |
Following today's incident: #5005 a few workspaces and prebuilds got stuck in a bad state.
Specifically, they have a workspace instance stuck in
phase = 'preparing'
, even though no build is in progress (anymore) -- and they have remained in this "temporary" state for several hours at least.It would be great to forcefully stop them again, so that they can be restarted, e.g. from an earlier backup.
The text was updated successfully, but these errors were encountered: