You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If infrastructure fails to delete, it's impossible to remove a workspace from Coder forcefully.
It's unclear what to do at this point because I'm happy forcefully drop the infrastructure here (in this case a Docker image reference). Maybe after build failure, we allow a force deletion if you're an admin?
I wonder if on the back end we want to allow replacing an existing workspace if we pass in the equivalent of --force. The initial issue here should be fixed cleanly, but I wonder about other inconsistent state issues that may arise.
kylecarbs
changed the title
Workspace failed during creation, but still creates a workspace in Coder's database, which prevents me from re-creating without deleting the dead workspace
Failed workspaces cannot be deleted, because the delete fails too
Aug 24, 2022
Uh oh!
There was an error while loading. Please reload this page.
Addition from @kylecarbs 👋
If infrastructure fails to delete, it's impossible to remove a workspace from Coder forcefully.
It's unclear what to do at this point because I'm happy forcefully drop the infrastructure here (in this case a Docker image reference). Maybe after build failure, we allow a force deletion if you're an admin?
@mafredri I'd love your thoughts!
Expected state: Rollback and do not create metadata for the workspace in Coder if the create fails.
The text was updated successfully, but these errors were encountered: