-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
Terraform Crash #31536
Comments
Hi @jchenseated, Thanks for reporting the issue! We are going to need more information here, specifically a configuration which can reproduce the crash. The best place to start looking is with whatever changes were most recently made to the config, including changing versions of providers. Looking at the core trace logs may help too, chances are that the resource config which was involved in the crash logged something right before that point which could help narrow things down. Taking shot in the dark, something with Thanks! |
Thank you @jbardin ! I followed your guideline and was able to pinpoint the issue to our appmesh resource's dynamic backend block. Here is the resource block code. I fixed the issue by manually removing the backend resource we configured on AWS UI. No terraform code changes needed. Whenever we added the backend resource on AWS UI, the error came back. Not sure what's the root cause for this, might be a provider issue. Thank you anyway!
|
Thanks for the added context @jchenseated. I have not yet been able to piece together how this example could create a null nested block at any level here. If a provider is involved in the error, there may be warnings logged about the specific resources, and looking for At this point my only hypothesis is a misbehaving legacy provider combined with |
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. |
Terraform Version
Terraform Configuration Files
We use terraform to map our entire infrastructure which expands across multiple aws module
Debug Output
Actual Behavior
We started to run into issue without new commit to the code base. The last commit was planned and applied without crash.
Additional Context
I am submitting this issue so I hopefully can get a direction to debug (for example, which module should I target based on the console error)
The text was updated successfully, but these errors were encountered: