-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Error replace nat - old nat don't delete before create new #999
Comments
We're encountering this as well when trying to increase our resilience by upgrading from one NAT Gateway to one in each AZ. Just changing from |
This issue has been automatically marked as stale because it has been open 30 days |
This issue was automatically closed because of stale in 10 days |
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. |
Description
Error replace nat.
If change variable in vpc, for example - add new subnet:
old variable:
in plan replaced nat (why?):
error:
In web i see my first nat:
test-vpc-eu-central-1a
nat-0590a6b4080c7c243
State: Available
And new nat:
test-vpc-eu-central-1a
nat-0712140e39ce85037
State: Failed
State message: Elastic IP address [eipalloc-032fbdcc109bc94ec] is already associated
Terraform do not delete nat before create new. If i manualy delete nat, then terraform apply is successful
Versions
Reproduction Code [Required]
Variables:
Module:
Terminal Output Screenshot(s)
After add new subnet:
The text was updated successfully, but these errors were encountered: