Skip to main content
NetApp Knowledge Base

Unable to change VM size with error : operation Start Vm failed Error

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

Applies to

  • BlueXP
  • Azure Cloud Volumes ONTAP

Issue

When attempting to change the VM size of a Cloud Volumes ONTAP node in Azure from `Standard_E8ds_v5` to `Standard_E20ds_v5`, the operation failed, and the node did not come back online. The following error message was observed:

Error "1" : Operation Start Vm failed Error: Code: OverconstrainedZonalAllocationRequest Target: null Message: 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

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.