Skip to content
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

aws_lb Data Source returns error setting subnet_mapping: Invalid address to set: []string{"subnet_mapping", "0", "private_ipv4_address"} #14565

Closed
ghost opened this issue Aug 11, 2020 · 5 comments · Fixed by #14545
Labels
bug Addresses a defect in current functionality. regression Pertains to a degraded workflow resulting from an upstream patch or internal enhancement. service/elbv2 Issues and PRs that pertain to the elbv2 service.
Milestone

Comments

@ghost
Copy link

ghost commented Aug 11, 2020

This issue was originally opened by @kartik-moolya as hashicorp/terraform#25806. It was migrated here as a result of the provider split. The original body of the issue is below.


Terraform Version

Terraform v0.12.29

Terraform Configuration Files

data "aws_lb" "nginxlb" {
  arn = var.nginx_lb_arn
  name = "mvp-ui-nginx-NLB"
}

Debug Output

https://gist.github.com/kartik-moolya/7f8d657aec8990eef2707565c4e77f8e

Crash Output

Expected Behavior

The Data should have imported the LB details

Actual Behavior

Got the below error

Error: error setting subnet_mapping: Invalid address to set: []string{"subnet_mapping", "0", "private_ipv4_address"}

  on main.tf line 39, in data "aws_lb" "nginxlb":
  39: data "aws_lb" "nginxlb" {

Steps to Reproduce

  1. terraform init
  2. terraform apply

Additional Context

The loadbalancer is a public Network load balancer and was created using cloudformation

References

@ghost ghost added the service/elbv2 Issues and PRs that pertain to the elbv2 service. label Aug 11, 2020
@github-actions github-actions bot added the needs-triage Waiting for first response or review from a maintainer. label Aug 11, 2020
@ewbankkit
Copy link
Contributor

@kartik-moolya Thanks for raising this issue.
There is a PR to address this issue, #14545, scheduled for the upcoming v3.2.0 release.

@ewbankkit ewbankkit added bug Addresses a defect in current functionality. regression Pertains to a degraded workflow resulting from an upstream patch or internal enhancement. and removed needs-triage Waiting for first response or review from a maintainer. labels Aug 11, 2020
@kartik-moolya
Copy link

@kartik-moolya Thanks for raising this issue.
There is a PR to address this issue, #14545, scheduled for the upcoming v3.2.0 release.

Thankyou for a quick response. Do you have any estimate on when can the fix be ready?

@bflad bflad added this to the v3.2.0 milestone Aug 13, 2020
@bflad
Copy link
Contributor

bflad commented Aug 13, 2020

The fix for this has been merged and will release with version 3.2.0 of the Terraform AWS Provider, later today. Thanks to @DrFaust92 for the implementation. 👍

@ghost
Copy link
Author

ghost commented Aug 14, 2020

This has been released in version 3.2.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 for triage. Thanks!

@ghost
Copy link
Author

ghost commented Sep 13, 2020

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!

@ghost ghost locked and limited conversation to collaborators Sep 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality. regression Pertains to a degraded workflow resulting from an upstream patch or internal enhancement. service/elbv2 Issues and PRs that pertain to the elbv2 service.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants