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

EIP deletion is not detected, unable to recover via taint #1529

Closed
ksperling opened this issue Aug 29, 2017 · 1 comment · Fixed by #1551
Closed

EIP deletion is not detected, unable to recover via taint #1529

ksperling opened this issue Aug 29, 2017 · 1 comment · Fixed by #1551
Labels
bug Addresses a defect in current functionality.

Comments

@ksperling
Copy link

Terraform Version

Terraform v0.10.2
AWS provider v0.1.4

Affected Resource(s)

  • aws_eip

Terraform Configuration Files

resource "aws_eip" "prod-otacontrol" {
  vpc = true
}

Expected and Actual Behavior

When the resource is deleted externally, terraform refresh should pick this up and recreate the resource. However the InvalidAllocationID.NotFound for the EIP is silently ignored and Terraform assumes the EIP still exists.

Trying to remedy the situation manually via terraform taint also does not work; When attempting to delete the (non-existant) EIP, Terraform keeps retrying to perform a ReleaseAddress indefinitely.

Debug Output

https://gist.github.com/ksperling/f5aeec3b59dd2f423904df58a8801ff0

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

  1. Create an EIP via Terraform (plan / apply)
  2. Delete the EIP via AWS console
  3. Terraform refresh / plan. Observe EIP deletion is not detected.
  4. Attempt to recover via taint / plan / apply also does not work.

References

The bug seems to have been introduced in this commit e4244f8 as part of #1053

When the EIP is not found in the "existing resource" code path, d.SetId("") needs to be called.

@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 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 Apr 11, 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.
Projects
None yet
2 participants