-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Updating azurerm_application_gateway fails with Duplicate address error #2894
Comments
i've experienced similar output, and (although my requirements are slightly different) i think it's the same issue. i have a backend address pool configured like this:
e.g. (edited to remove identifiers)
as far as i can tell, this is related to the internal handling of BackendAddresses, Fqdns and FqdnList within the expand/flatten methods in azurerm/resource_arm_application_gateway.go. there are deprecations in play, it's possible that's a factor. the same internal variable is being used to populate both the 'old' and the 'new' keys:
this led me to a possible workaround... if i also specify the fqdn_list, but with a dummy value, i can get a clean
@Ashex similarly, you might have some luck with also setting |
update: the above workaround ran into issues for me with HTTPS backends :( |
For me the only working workaround is to provide one or multiple ip adresses for |
Same dang problem. Thanks for the suggested work-arounds. |
Bugs like this makes it pretty hard to automate and lock down an environment. Adding the dummy does get me around a problem, but then I now have an invalid backend pool entry, so need to do two separate released to get it fixed. I got it trying to fix an issue with fixing a probe and http setting to move to the "pick_host_name*' settings, and got this. |
Stuck with the same....unfortunately.... |
Trying to simply add tags to an application gateway and getting the same error. |
Same here. My workaround was to set it to dummy like the above suggests. It did then have two fqdns for each address pool. I then went into Resource Explorer, and modified the gateway there, removing dummy from the list for each address pool. This is really cumbersome and I hope this gets bumped up on the priority list for getting fixed. Another note, the waf_configuration.0.file_upload_limit_mb, no matter what you set it to, always gets set back to 0, so will see it as a change every time on the app gateway. I think this will be fixed in 1.24.0, something about it is referenced there. I put in a lifecycle to ignore_changes so it stops and made a note to test it again when 1.24.0 is out. |
This has been released in version 1.24.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 1.24.0"
}
# ... other configuration ... |
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. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
Community Note
Terraform (and AzureRM Provider) Version
Terraform v0.11.11
Affected Resource(s)
azurerm_application_gateway
Terraform Configuration Files
Debug Output
https://gist.github.com/Ashex/e52694f8b96599b5208f084adf6c9fe5
Expected Behavior
Updating any attribute of the azurerm_application_gateway should succeed or throw an error related to that attribute
Actual Behavior
All changes return the following error:
Indicating that the same address is being added to a single address pool twice, which is not happening here.
Steps to Reproduce
terraform apply
to create application gatewayterraform apply
Important Factoids
Downgrading the provider to 1.21 allows me to update the application gateway without encountering this error.
References
The text was updated successfully, but these errors were encountered: