Closed tompahoward closed 5 years ago
Here's with TF_LOG=trace https://gist.github.com/tompahoward/0e8711449b48bcd24e0ca273ab4d7df8
It's also worth noting that the workspace for this is used as a smoke-test for the deployment. For every commit that build's successfully we do deploy (using plan
and apply
) and then we destroy it (using plan --destroy
and apply
). As I haven't see this error with other environments, I'm wondering if it's the constant create and destroy that triggers this defect.
I caused the same by manually deleting (Vultr) servers that were listed deposed in tfstate. Removing them from state (manually) sorted it.
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
Terraform Configuration Files
main.tf
versions.tf
provider.tf
superlife.tf
Debug Output
https://gist.github.com/tompahoward/3776b869694c75630fcfb9a9962e9dc8
Crash Output
https://gist.github.com/tompahoward/e2d4e41dc99e263b7dd0e8ea1e72e30e
Expected Behavior
Not crash
Actual Behavior
Crashed
Steps to Reproduce
Workspace is in a strange stage. Previously did and
plan
andapply
. Now when trying to taint an was instance, it fails withSo trying to figure out what's going on. ran
terraform refresh
andterraform show
. The later resulted in the crash.Additional Context
References