Skip to main content
NetApp Knowledge Base

Azure HA CVO deployment fails due to Zone Constraint

  1. Last updated
    Jun 5, 2025
  2. Save as PDF
Views:
30
Visibility:
Public
Votes:
0
Category:
cloud-manager
Specialty:
bluexp
Last Updated:
6/5/2025, 4:30:47 AM

Applies to

  • BlueXP
  • Cloud Volumes ONTAP (CVO)
  • Microsoft Azure

Issue

  • Azure HA CVO fails deployment with the following error
 
Error:Operation Deploy Load Balancer Template failed Deployment of xx-xx-xx-cc-lb from type Microsoft.Network/loadBalancers failed with status BadRequest code: ResourceAvailabilityZonesCannotBeModified target: null message: Resource /subscriptions/xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx/resourceGroups/ban-pr-rg-cc/providers/Microsoft.Network/loadBalancers/xxx-xx-rg-cc-lb/frontendIPConfigurations/clusterMgmtFIP has an existing availability zone constraint 1, 2, 3 and the request has availability zone constraint 1, which do not match. Zones cannot be added/updated/removed once the resource is created. The resource cannot be updated from regional to zonal or vice-versa.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.