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

provider/aws: Allow IPv6/IPv4 addresses to coexist #13702

Merged
merged 1 commit into from
May 31, 2017

Conversation

bryanburgers
Copy link
Contributor

@bryanburgers bryanburgers commented Apr 17, 2017

Fix an issue when trying to get a public IPv4 address and a public IPv6
address that results in the following error:

Error launching source instance: InvalidParameterCombination:
Network interfaces and an instance-level IPv6 address count may not
be specified on the same request

To fix, in situations where we want a IPv6 addresses AND we need to
manually specify network interfaces on the instance, create the IPv6
addresses on the network interface that we're creating rather than on
the instance itself.

Fixes #13250

@bryanburgers bryanburgers force-pushed the aws-instance-ipv6 branch 3 times, most recently from ae417f0 to 62acf59 Compare April 17, 2017 13:47
@bryanburgers bryanburgers changed the title WIP: Allow IPv6 addresses and IPv4 addresses to coexist provider/aws: Allow IPv6/IPv4 addresses to coexist Apr 17, 2017
@bryanburgers
Copy link
Contributor Author

bryanburgers commented Apr 17, 2017

I was unable to figure out how to get make test TEST=./builtin/providers/aws to work properly on my computer – even on master without my code – so I'm not highly confident in my acceptance test. However I did add an acceptance test and Travis succeeded. Maybe if I can get some other eyes on it?

@bryanburgers
Copy link
Contributor Author

@stack72 You seem like a person that knows the AWS code well. Can you give me your thoughts on this PR?

@bryanburgers
Copy link
Contributor Author

@mbfrahry @grubernaut I rebased this onto master to bring it up-to-date again. Can I get one of you to give this a review?

@grubernaut grubernaut requested a review from stack72 May 2, 2017 13:24
Fix an issue when trying to get a public IPv4 address and a public IPv6
address that results in the following error:

    Error launching source instance: InvalidParameterCombination:
    Network interfaces and an instance-level IPv6 address count may not
    be specified on the same request

To fix, in situations where we want a IPv6 addresses AND we need to
manually specify network interfaces on the instance, create the IPv6
addresses on the network interface that we're creating rather than on
the instance itself.

Fixes hashicorp#13250
@catsby catsby requested a review from grubernaut May 31, 2017 12:15
@grubernaut
Copy link
Contributor

Hey @bryanburgers, thanks for the contribution!

In order to run acceptance tests, the testacc makefile target needs to be used:

$ make testacc TEST=./builtin/providers/aws TESTARGS="-run=TestAccAWSInstance_ipv6_supportAddressCountWithIpv4"
==> Checking that code complies with gofmt requirements...
go generate $(go list ./... | grep -v /terraform/vendor/)
2017/05/31 10:03:40 Generated command/internal_plugin_list.go
TF_ACC=1 go test ./builtin/providers/aws -v -run=TestAccAWSInstance_ipv6_supportAddressCountWithIpv4 -timeout 120m
=== RUN   TestAccAWSInstance_ipv6_supportAddressCountWithIpv4
--- PASS: TestAccAWSInstance_ipv6_supportAddressCountWithIpv4 (144.70s)
PASS
ok      github.com/hashicorp/terraform/builtin/providers/aws    144.724s

Copy link
Contributor

@grubernaut grubernaut left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@grubernaut grubernaut merged commit 647a394 into hashicorp:master May 31, 2017
@ghost
Copy link

ghost commented Apr 11, 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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

provider/aws: Can't create an aws_instance in a VPC with an auto-generated IPv6 address
3 participants