-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
panic in aws/resource_aws_instance.go in v3.25.0 #17284
Comments
terraform-provider-aws/aws/resource_aws_instance.go Lines 930 to 932 in 431cf30
calling terraform-provider-aws/aws/resource_aws_instance.go Lines 1655 to 1673 in 431cf30
terraform-provider-aws/aws/resource_aws_instance.go Lines 1732 to 1747 in 431cf30
terraform-provider-aws/aws/resource_aws_instance.go Lines 1797 to 1805 in 431cf30
|
I did build the provider with my proposed fix (just testing for that elb list being nil). make test works and my terraform plan completes without incident. |
Hi @jayalane 👋 Thank you for raising this and sorry you ran into trouble here. If you want to submit your proposed code patch, which looks okay, the maintainers can handle additional testing and get the fix out tomorrow. Thanks again. |
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. |
My account is getting panic in line 1665 of version v3.25.0 of aws/resource_aws_instance.go
The backtrace is:
I have no idea what's going on, but seems panic is prima facie bug. I'm testing this fix on my local provider:
Community Note
Terraform CLI and Terraform AWS Provider Version
Affected Resource(s)
It is crashing during plan before it starts updating what the plan would do, walking the dag I guess. I ran it under TF_LOG=1 but the immediate logging around the panic lines don't seem related to aws_instance resource. I can't just put the whole config out here.
Terraform Configuration Files
I won't be able to upload all the terraform config. If I can reproduce it in a smaller set, I'll submit that. I will also note here if my proposed patch fixes the issue.
Debug Output
Panic Output
I can't find a crash.log but the panic and backtrace are above.
Expected Behavior
Successful apply.
Actual Behavior
Lot of output like:
Steps to Reproduce
terraform apply
Important Factoids
Biggish? 3133 lines of tf, 532 items in 'terraform state list' and 47 ec2. Mostly just vanilla S3 and Ec2. More VPC and subnets than our normal accounts (multi-tenant SaaS implementation).
References
The text was updated successfully, but these errors were encountered: