-
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
Workspaces are stuck in stopping #4156
Comments
I'd think this has to do with the runc/containerd issue we're working around in ws-daemon because of containerd 1.2.10 |
@csweichel do you mean this workaround here?
I tried to find log entries to see the workaround working/failing for the workspaces mentioned above, but it appears there is no trace of them besides updates of labels. |
See #4171 |
We still see regular workspace start failures, that leave workspaces in a state where user can no longer start them. |
Also users themselves should be able to stop workspaces. Currently it seems like the stop request just fails because ws-man doesn't find the pod anymore. |
/assign |
/schedule |
Looked at with @csweichel. Seems the node and cluster have been destroyed and this issue has been fixed subsequently. See #4683 and #5130 |
on node gke-gp-ws-us04-us-west-workspace-pool-7059fb33-x2dc,
we have a bunch of pods that show up in
crictl pods
but not inkubectl get pod
:not sure what's preventing them from stopping. I became aware of them due to an out-of-disk-space-alert. I suspect they fill up the logs leading to #4135.
The text was updated successfully, but these errors were encountered: