Skip to main content
NetApp Knowledge Base

CVO Azure VMs fails to starts in Azure due to resource allocation constraints

  1. Last updated
  2. Save as PDF
Views:
19
Visibility:
Public
Votes:
0
Category:
cloud-manager
Specialty:
bluexp
Last Updated:

Applies to

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

Issue

  • CVO VMs fails to start in Microsoft Azure with error below:
Failed to start virtual machine 'cvo-vm1'. Error: Allocation failed. VM(s) with the following constraints cannot be allocated, because the condition is too restrictive. Please remove some constraints and try again. Constraints applied are:
- Availability Zone
- Networking Constraints (such as Accelerated Networking or IPv6)
- VM Size  
  • This behaviour is seen after the VM has been deallocated in Azure following a manual or automatic/programmatic VM stop action.

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.