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
Describe the bug
There is a typo in an error message:
E1220 12:16:22.587762 1 controller.go:142] network.ApplicationGatewaysClient#CreateOrUpdate: Failure sending request:
StatusCode=400 -- Original Error: Code="ApplicationGatewayBackendAddressPoolInUseByVirtualMachineScaleSet"
Message="Cannot remove backend address pool XXXXXXXX from applciation gateway /subscriptions/XXXXXXXXXXX/resourceGroups/XXXXXX/providers/Microsoft.Network/applicationGateways/XXXXXXXXXX
because it is in use by virtual machine scale set /subscriptions/XXXXXXXXXXX/resourceGroups/XXXXXXXX/providers/Microsoft.Compute/virtualMachineScaleSets/XXXXXXXXXXXXX." Details=[]
E1220 12:16:22.587774 1 worker.go:62] Error processing event.network.ApplicationGatewaysClient#CreateOrUpdate: Failure sending request: StatusCode=400 --
Note the applciation gateway in third line.
To Reproduce
The situation per-si that caused the error it's irrelevant, here, but someone added manually a backend pool to a vm scaleset and then when the ingress-controller tried to update the application gateway, the backend could not be removed (the scaleset is running).
This seems to be the response coming from an azure API, not the ingress controller itself (I couldn't find this string anywhere in this code), but I suppose you can open the ticket internally.
The text was updated successfully, but these errors were encountered:
Describe the bug
There is a typo in an error message:
Note the
applciation gateway
in third line.To Reproduce
The situation per-si that caused the error it's irrelevant, here, but someone added manually a backend pool to a vm scaleset and then when the ingress-controller tried to update the application gateway, the backend could not be removed (the scaleset is running).
This seems to be the response coming from an azure API, not the ingress controller itself (I couldn't find this string anywhere in this code), but I suppose you can open the ticket internally.
The text was updated successfully, but these errors were encountered: