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

[ws-manager] Properly stop workspaces that time out during backup #4937

Closed
csweichel opened this issue Jul 25, 2021 · 1 comment · Fixed by #4943
Closed

[ws-manager] Properly stop workspaces that time out during backup #4937

csweichel opened this issue Jul 25, 2021 · 1 comment · Fixed by #4943
Labels
component: ws-manager groundwork: awaiting deployment operations: past incident This issue arose during a past incident or its post-mortem priority: highest (user impact) Directly user impacting type: bug Something isn't working

Comments

@csweichel
Copy link
Contributor

Bug description

Right now when a workspace times out during backup it remains "stuck in terminating" because we don't set the disposal status annotation, and hence don't remove the finalizer.

Steps to reproduce

Have the workspace time out in backup, e.g. due to a ws-daemon failure.

Expected behavior

The workspace should stop properly.

Example repository

No response

Anything else?

No response

@csweichel csweichel added type: bug Something isn't working component: ws-manager labels Jul 25, 2021
@csweichel csweichel added operations: past incident This issue arose during a past incident or its post-mortem priority: highest (user impact) Directly user impacting labels Jul 25, 2021
@csweichel
Copy link
Contributor Author

/schedule

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: ws-manager groundwork: awaiting deployment operations: past incident This issue arose during a past incident or its post-mortem priority: highest (user impact) Directly user impacting type: bug Something isn't working
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants