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
Unable to destroy resources in workspace after workspace removal warning #24019
Comments
Additionally, after running
|
Hello @pselle |
This has been resolved, please close it. |
This will be included in the next 0.12 release. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Terraform Version
Built from #22540
Terraform Configuration Files
Debug Output
https://gist.github.com/pselle/6f8dc4f1ae686398f92b2b6a9a7aade9
Crash Output
Expected Behavior
Should be able to destroy objects in workspace
Actual Behavior
State lock is lingering
Steps to Reproduce
space3
) populated with objectsterraform workspace select default
go to a different workspaceterraform workspaces delete space3
try to delete the workspace, you'll get an error that there are objects remaining, and that it could create lingering objects.terraform workspace select space3
terraform destroy
Unable to destroy objects, as a state lock is present. This is present through multiple runs/is consistent.Additional Context
The workflow above is should be able to re-create the error consistently. In addition to being unable to destroy objects in
space3
, any interaction in the workspacespace3
is now blocked by the lingering state lock (cannotapply
either)References
The text was updated successfully, but these errors were encountered: