-
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
failure to create aws_lb network load balancer resource #1946
Comments
likely it's same issue reported in a comment in #1912 - using a subnet_mapping causes creation to hang indefinitely. |
This was addressed in #1956 which was merged and will be available in the next release. |
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! |
Hi there,
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
Terraform Version
esolomon@olmint ~/github/onelogin-terraform-general/prod/haproxy $ terraform -v
Terraform v0.10.7
Affected Resource(s)
Please list the resources as a list, for example:
If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.
Terraform Configuration Files
Debug Output
none
Panic Output
none
Expected Behavior
creating Network Load Balancer
Actual Behavior
Resource never gets created. I've waited up to 20 minutes to see if it completes.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply tf.plan
Important Factoids
I've tried this in several AWS regions with the same behavior. The
count
conditional is a little hacky but necessary since we have a region with only two subnets active.References
The text was updated successfully, but these errors were encountered: