-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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 report #5963
Comments
Relevant portion of crash.log (no confidential data):
Stripped
The fix for the panic itself is straightforward (its always expecting |
The fix to prevent panics when the AMI state is failed has been merged into master and will release with version 1.38.0 of the AWS provider, likely middle of this week. |
This has been released in version 1.38.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
This issue was originally opened by @bennettp123 as hashicorp/terraform#18917. It was migrated here as a result of the provider split. The original body of the issue is below.
Terraform Version
(Also reproduced in v0.11.7, but the crash and trace logs provided below are from v0.11.8).
Terraform Configuration Files
Debug Output
https://gist.github.com/bennettp123/c2760fc5e0ff230431fcc08b96e97900#file-trace-log-enc
Crash Output
https://gist.github.com/bennettp123/7645f4c4a9f2b7c84b777e969f454297#file-crash-log-enc
Expected Behavior
Does not crash.
Actual Behavior
Crashes with crash.log and trace output attached
Steps to Reproduce
terraform init
terraform apply -out=.tfplan
Additional Context
References
The text was updated successfully, but these errors were encountered: