-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Network (2020-05-01): Error removing/updating load balancer rules #10104
Comments
I am also facing the same issue, please fix |
I just ran into this issue as well. I am pretty sure I didn't experience this until after implementing Scale Sets. But could be wrong. Error: Error Creating/Updating Load Balancer "lbi.example.example-poc.development.services" (Resource Group "rg.example.example-poc.development.services"): network.LoadBalancersClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="InvalidRequestFormat" Message="Cannot parse the request." Details=[{"code":"DuplicateIpConfigurationReferenceOnBackendAddressPool","message":"Found duplicate ipConfiguration reference /subscriptions/134b3809-76mf-4891-bf25-edfaf8d5fc6f/resourceGroups/rg.example.example-poc.development.services/providers/Microsoft.Network/networkInterfaces/nic-wpapp01.example.example-poc.development.services/ipConfigurations/ip-wpapp01.example.example-poc.development.services on backend pool addresses /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools//loadBalancerBackendAddresses/ and /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools/lbi-wpapp.example.example-poc.development.services/loadBalancerBackendAddresses/0af31b77-ec08-4910-a328-66fe0662a851."},{"code":"DuplicateIpConfigurationReferenceOnBackendAddressPool","message":"Found duplicate ipConfiguration reference /subscriptions/134b3809-76mf-4891-bf25-edfaf8d5fc6f/resourceGroups/rg.example.example-poc.development.services/providers/Microsoft.Network/networkInterfaces/nic-wpapp02.example.example-poc.development.services/ipConfigurations/ip-wpapp02.example.example-poc.development.services on backend pool addresses /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools//loadBalancerBackendAddresses/ and /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools/lbi-wpapp.example.example-poc.development.services/loadBalancerBackendAddresses/e7c37c29-a3ac-403d-b234-a74009841b8a."}] |
We have the same problem, please fix |
This also affects any regular VMs in a Standard LB's backend pool Error: Error Creating/Updating Load Balancer "LB-TEST01" (Resource Group "RGP-TESTAZURERMv2"):
network.LoadBalancersClient#CreateOrUpdate: Failure sending request: StatusCode=400 --
Original Error:
Code="InvalidRequestFormat"
Message="Cannot parse the request."
Details=[{
"code":"DuplicateIpConfigurationReferenceOnBackendAddressPool",
"message":"Found duplicate ipConfiguration reference /subscriptions/xxxxxx-xxxx-xxxx-xxxx-xxxxxx/resourceGroups/RGP-TESTAZURERMv2/providers/Microsoft.Network/networkInterfaces/vmtest01_nic-eth0/ipConfigurations/vmtest01-SubnetIPConfig on backend pool addresses /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools//loadBalancerBackendAddresses/ and /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools/LB-TEST01-backend_pool/loadBalancerBackendAddresses/xxxxxx-xxxx-xxxx-xxxx-xxxxxx."},
{"code":"DuplicateIpConfigurationReferenceOnBackendAddressPool",
"message":"Found duplicate ipConfiguration reference /subscriptions/xxxxxx-xxxx-xxxx-xxxx-xxxxxx/resourceGroups/RGP-TESTAZURERMv2/providers/Microsoft.Network/networkInterfaces/vmtest02_nic-eth0/ipConfigurations/vmtest02-SubnetIPConfig on backend pool addresses /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools//loadBalancerBackendAddresses/ and /subscriptions//resourceGroups//providers/Microsoft.Network/loadBalancers//backendAddressPools/LB-TEST01-backend_pool/loadBalancerBackendAddresses/xxxxxx-xxxx-xxxx-xxxx-xxxxxx."
}] |
You can temporarily lock down the azurerm module to version 2.17.0, it is still using the older Azure API and does not have this problem. |
So this is interesting, I am using
|
According to https://www.terraform.io/docs/configuration/modules.html#module-versions with "~> 2.15" you are allowing any version up to (excluding) 3.0.0. So, most likely you are using right now 2.19, which is the highest available one < 3.0.0 |
That is actually true. Thanks for catching that! |
Btw, just in case it matters for some one, the same issue exist with managing LB health checks - same exact issue, and same (temporary) fix. |
Saw this there as well. I am about to kick off a pipeline build to see if this solves the issues I've experienced as well. Just to clarify, I have pinned the provider to
|
Curious whether this is related as well. I have put in |
Just as an FYI. I have gone through pipeline several times now with success using UPDATE - The fourth teardown has gone into a race condition. So, maybe not related. |
This one is still active and present :( Test case - deploy Azure Loadbalancer
-> now create another backend pool or even a separate frontend and the same setup on the existing one Error output:
|
@ArcturusZhang can we get the "Service Attention" and "Load Balancer" labels on this one so the service team can look at this API bug? |
@ArcturusZhang Additionally, please check whether #10131 has already addressed that. |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @slbsupportgithub. |
any updates regarding this fix in new provider version/upstream API? |
Hi @gek0 this issue should have been fixed. I am going to close this issue. Please feel free to reopen this or comment if you see this issue again. |
Reopen per request |
#10131 doesn't actually fix this issue, this should be fixed on service side. |
👋 any update here? |
@tombuildsstuff Confirmed with service team, this has been fixed. I've created a PR hashicorp/terraform-provider-azurerm#10263 for the linked TF issue. |
When using 2020-05-01 network API, when I want to remove a load balancer rule that the load balancer is attached to VMSS, the request will fail.
The complete flow is as below:
GET https://management.azure.com/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1?api-version=2020-05-01 HTTP/2.0
PUT https://management.azure.com/subscriptions/0-0-0-0/resourceGroups/test-hbtest/providers/Microsoft.Network/loadBalancers/hbtest1?api-version=2020-05-01 HTTP/2.0
Response:
The text was updated successfully, but these errors were encountered: