You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Terraform Version
Terraform v0.10.2
AWS provider v0.1.4
Affected Resource(s)
Terraform Configuration Files
Expected and Actual Behavior
When the resource is deleted externally,
terraform refresh
should pick this up and recreate the resource. However theInvalidAllocationID.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 aReleaseAddress
indefinitely.Debug Output
https://gist.github.com/ksperling/f5aeec3b59dd2f423904df58a8801ff0
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
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.The text was updated successfully, but these errors were encountered: