Skip to content

Allow users to "force stop" workspaces which are stuck in stopping #8420

Closed
@kylos101

Description

@kylos101

Is your feature request related to a problem? Please describe

This generally happens if the pod backing the related workspace enters a bad state while stopping.

Describe the behaviour you'd like

After some preconditions (an hour being in stopping?), grant the user the ability to force stop their workspace through the dashboard.

Why? This gives the user the ability to access their workspace and files w/o needing manual intervention from Gitpodders.

If this feature is used, we should track it via some metric, so we can understand how often it is being used.

Also, we should consider displaying a warning to the user, prior to using. For example, it is possible their backup is not done. So, if they were to force stop a workspace, and start a new instance, it could load a backup with N-1 data.

Another interesting idea is option #3 (below). It's less destructive, and the user would also be able to add those files to a new workspace, w/o potentially disrupting a long running backup.

Describe alternatives you've considered

  1. Rely on personnel to manually fix such conditions via the database. This is not ideal because it is error prone and creates a significant delay between the user and them accessing their files for the workspace. Plus, some users may not even be reaching out for support, and just lose their data.
  2. Automatically force stop any regular workspace which are stuck in stopping after some precondition.
  3. Give the user the ability to download their files, w/o having the ability to force stop a workspace.
  4. Add a Force Stop button to the admin page, and have personnel use this button (rather than a database query)

Additional context

#7597 (comment)

Front logo Front conversations

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    In Validation

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions