Terraform: EIP reallocation failure

Created on 2 May 2016  ยท  5Comments  ยท  Source: hashicorp/terraform

Hi,

Since the v0.6.15 release terraform cannot reassociate elastic IPs.

Terraform Version

Fails on Terraform v0.6.15
Succeeds on Terraform v0.6.14

Affected Resource(s)

  • aws_eip

    Terraform Configuration Files

Changing config from:

resource "aws_eip" "default" {
  vpc = true
  instance = "${aws_instance.instance_a.id}"
}

to:

resource "aws_eip" "default" {
  vpc = true
  instance = "${aws_instance.instance_b.id}"
}

Debug Output

TRACE log

Expected Behavior

The EIP should be reassociated with the new instance

Actual Behavior

Terraform fails with:

aws_eip.default: Failure associating EIP: InvalidParameterValue: 10.x.x.x is not mapped to the interface eni-xxxxxxxx

Steps to Reproduce

  1. set existing aws_eip.instance to a new value
  2. terraform apply
bug provideaws

All 5 comments

Also affected by this

Ran in to this as well.

@cstruct Thanks for taking the time to write up a thorough bug report. I wasn't certain if I was doing something stupid with AWS or if this was an issue...

Hey @cstruct thanks for opening this!

6521 should fix this. Note that if you're using private_ip in your EIP resource, you'll need to use the new associate_with_private_ip attribute that's added in that pull request

Thank you @catsby

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.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

rjinski picture rjinski  ยท  3Comments

pawelsawicz picture pawelsawicz  ยท  3Comments

shanmugakarna picture shanmugakarna  ยท  3Comments

c4milo picture c4milo  ยท  3Comments

zeninfinity picture zeninfinity  ยท  3Comments