-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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 fails when adding multiple secondary private ip addresses #16477
Comments
terraform-provider-aws/aws/resource_aws_instance.go Lines 1598 to 1600 in 79e4383
terraform-provider-aws/aws/resource_aws_instance.go Lines 1679 to 1681 in 79e4383
|
@arthar360 Thanks for raising this issue. |
Thanks @ewbankkit , setting |
This functionality has been released in v3.74.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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.13.5
Terraform Configuration Files
Instead of
aws_network_interface = element(aws_network_interface.test[*].id, 1)
I have also triedaws_network_interface = aws_network_interface.test[1].id
. It returns the same error.Debug Output
https://gist.github.com/arthar360/02f25e4a1f272ae443a29ee1aa525d00
Panic Output
crash.log
Expected Behavior
The 2 ec2 instances should have been created with 3 private ip addresses each.Actual Behavior
Terraform created successfully and failed with error
On subsequent terraform apply, Terraform crashes. Please refer to debug gist for that
It is also strange to notice that instance id's shown in
Creation complete after 23s [id=i-062af6a475130f9bf]
andCreation complete after 33s [id=i-0b0351f427c10c57e]
are different than
Error waiting for instance (i-09baa706e3364263e) to become ready
andError waiting for instance (i-0b72b8b6e25a9c41a) to become ready
References
The text was updated successfully, but these errors were encountered: