Skip to content
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.

Sign up for GitHub

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

Jump to bottom

az network lb --frontend-ip-zone not working when multiple zones are included #30502

Open
cozhang8 opened this issue Dec 10, 2024 · 12 comments · May be fixed by #30639
Open

az network lb --frontend-ip-zone not working when multiple zones are included #30502

cozhang8 opened this issue Dec 10, 2024 · 12 comments · May be fixed by #30639
Assignees
@necusjz @Jing-song
Labels
Auto-Assign Auto assign by bot 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 Service Attention This issue is responsible by Azure service team.
Milestone
Backlog

Comments

@cozhang8
Copy link

Describe the bug

Customer is unable to deploy Azure Load Balancer when the frontend-ip-zone is set to multiple zones. They are able to deploy with no issues when frontend-ip-zone 1. It doesn't seem to be an issue from networking side since the same deployment can be completed in Portal.

Related command

az network lb --frontend-ip-zone

Errors

...which uses zone Zone-redundant since subscription xxxxxxx does not support zone Zone-redundant in location canadacentral."

Issue script & Debug output

az network lb create
--resource-group $resourcegroup
--name $lb_name
--sku Standard
--vnet-name $vnet_name
--subnet $subnet_name
--frontend-ip-name $lb_frontendip_name
--frontend-ip-zone 1,2,3 \ <--
--backend-pool-name $lb_backend_pool_name

Expected behavior

Deployment should not have an error when using --frontend-ip-zone 1,2 or --frontend-ip-zone 1,2,3 since these zones exist and the same zone deployments work in Portal.

Environment Summary

to be included by the SE

Additional context

No response
@cozhang8 cozhang8 added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Dec 10, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. Network az network vnet/lb/nic/dns/etc... labels Dec 10, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added Auto-Assign Auto assign by bot Azure CLI Team The command of the issue is owned by Azure CLI team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Dec 10, 2024
@yonzhan
Copy link
Collaborator

yonzhan commented Dec 10, 2024

Thank you for opening this issue, we will look into it.

@yonzhan yonzhan added this to the Backlog milestone Dec 10, 2024
@yonzhan yonzhan removed the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Dec 10, 2024
@necusjz
Copy link
Member

necusjz commented Dec 10, 2024

please provide the whole error message, especially including the error code.

@cozhang8
Copy link
Author

updated the error message/code

@WholeWhitebread
Copy link

Is there any update on this issue?

{"status":"Failed","error":{"code":"DeploymentFailed","target":"/subscriptions/d5176ebb-96da-4847-940f-dc9cd320f797/resourceGroups/lbtest/providers/Microsoft.Resources/deployments/lb_deploy_YGTe67RoPUMLiDa4Hy10DykkF1tf3HmK","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"SubscriptionDoesNotSupportZone","message":"Cannot create/move resource /subscriptions/d5176ebb-96da-4847-940f-dc9cd320f797/resourceGroups/lbtest/providers/Microsoft.Network/loadBalancers/testinglb/frontendIPConfigurations/frontend which uses zone 1,2,3 since subscription d5176ebb-96da-4847-940f-dc9cd320f797 does not support zone 1,2,3 in location canadacentral.","details":[]}]}}

@WholeWhitebread
Copy link

@necusjz @yonzhan Any Update?

@necusjz necusjz added the Service Attention This issue is responsible by Azure service team. label Dec 30, 2024
@necusjz
Copy link
Member

necusjz commented Dec 30, 2024

Is there any update on this issue?

{"status":"Failed","error":{"code":"DeploymentFailed","target":"/subscriptions/d5176ebb-96da-4847-940f-dc9cd320f797/resourceGroups/lbtest/providers/Microsoft.Resources/deployments/lb_deploy_YGTe67RoPUMLiDa4Hy10DykkF1tf3HmK","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"SubscriptionDoesNotSupportZone","message":"Cannot create/move resource /subscriptions/d5176ebb-96da-4847-940f-dc9cd320f797/resourceGroups/lbtest/providers/Microsoft.Network/loadBalancers/testinglb/frontendIPConfigurations/frontend which uses zone 1,2,3 since subscription d5176ebb-96da-4847-940f-dc9cd320f797 does not support zone 1,2,3 in location canadacentral.","details":[]}]}}

it's an error code from server side, added service team for help; and maybe you could try another region except canadacentral.

@yonzhan yonzhan removed the Azure CLI Team The command of the issue is owned by Azure CLI team label Dec 30, 2024
@WholeWhitebread
Copy link

WholeWhitebread commented Dec 30, 2024 •
edited
Loading

@necusjz @yonzhan

I have replicated this in different regions and it fails.

This only happens when trying to do it through CLI using command az network lb --frontend-ip-zone 1,2,3

I can create just fine with --frontend-ip-zone 1

Image

@WholeWhitebread
Copy link

@necusjz @yonzhan @jsntcy

Can you please provide an update to this bug as this is affecting customers. Thanks

@WholeWhitebread
Copy link

@necusjz @jsntcy @yonzhan @Jing-song

Can we please get an update on this issue or a timeframe when this will be fixed. Thanks!

@Jing-song Jing-song linked a pull request Jan 10, 2025 that will close this issue
Open
3 tasks
@Jing-song
Copy link
Contributor

Jing-song commented Jan 10, 2025 •
edited
Loading

Hi @WholeWhitebread , I have created a PR to fix it. PR link. Please note that parameters with multiple values are usually separated by spaces instead of commas.

Before that, you can try using
network lb frontend-ip create -g {rg} --lb-name {lb1} -n {name} -z 1 2 3 --vnet-name {vnet1} --subnet subnet
to add frontend ip zone for netowrk lb. Example

@WholeWhitebread
Copy link

@Jing-song Thanks

From my understanding the Network LB frontend-ipcreate can only happen after a LB is created, then you can run that command.

However I believe the end goal is to create lb and frontend Ip at the same time.

Appreciate the help looking into this.

@WholeWhitebread
Copy link

@Jing-song

Is there any ETA on when this command will be fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@necusjz necusjz

@Jing-song Jing-song

Labels
Auto-Assign Auto assign by bot 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 Service Attention This issue is responsible by Azure service team.
Projects
None yet
Milestone
Backlog
5 participants
@necusjz @Jing-song @yonzhan @WholeWhitebread @cozhang8