-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
Crash while destroying state #19740
Comments
Similar (same panic message |
We found that manually deleting the resources which reported that the plugin did not respond was a workaround to resolve the issue. |
Hi @aaron-lane , thank you for reporting this issue. Do you mind providing access to the workspace to see if there's anything we can find in the logs (if that's also viewabled?) when the |
Experiencing a similar issue during a destroy using version |
The similar with version 3.51.0
|
Hi @aaron-lane 👋 Terraform |
@justinretzolk I'll give it a whirl |
Thanks for confirming @aaron-lane! 🎉 With that in mind, we'll go ahead and close this issue. |
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. |
Community Note
Terraform CLI and Terraform AWS Provider Version
Terraform v0.15.4
AWS Provider v3.44.0
Affected Resource(s)
Resources reporting
Error: Plugin did not respond
:Resources reporting
Error: Request cancelled
:Terraform Configuration Files
https://github.com/hashicorp/terraform-aws-terraform-enterprise/tree/master/tests/private-tcp-active-active
Panic Output
https://gist.github.com/aaron-lane/c5b4f37486b94fc3293a33b95e573c23
Expected Behavior
Terraform should have successfully destroyed resources.
Actual Behavior
Terraform crashed while destroying resources.
Steps to Reproduce
terraform apply
successfully:terraform apply
unsuccessfully against the same state with different inputs for resource names:terraform destroy
unsuccessfully:Important Factoids
The applies were triggered by GitHub Actions and used a TFC workspace as the remote backend. The destroy was triggered manually via TFC. Access can be granted to the workspace as necessary.
The text was updated successfully, but these errors were encountered: