Cannot Attach Multiple Load balancer Front End IP Configurations to an Existing Private Link Service (PLS) #29305
Labels
Auto-Assign
Auto assign by bot
Azure CLI Team
The command of the issue is owned by Azure CLI team
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
Network
az network vnet/lb/nic/dns/etc...
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone
Describe the bug
Tried the following command to attach an additional load balancer front end IP configuration.
This resulted the following error.
However, the docs state that we can provide space separated list of IP configurations with
--lb-frontend-ip-configs
optionRelated command
az network private-link-service update
Errors
(InvalidNumberOfPrivateLinkServiceLoadBalancerFrontendIpConfigurationsSpecified) Cannot have more than one load balancer frontend IP configuration on the private link service. Private link service has 2 load balancer frontend IP configurations specified.
Code: InvalidNumberOfPrivateLinkServiceLoadBalancerFrontendIpConfigurationsSpecified
Message: Cannot have more than one load balancer frontend IP configuration on the private link service. Private link service has 2 load balancer frontend IP configurations specified.
Issue script & Debug output
Expected behavior
According to the docs it should allow us to provide multiple IP configurations with
--lb-frontend-ip-configs
optionEnvironment Summary
Additional context
No response
The text was updated successfully, but these errors were encountered: