Skip to main content
NetApp Knowledge Base

Azure CVO upgrade is taking too long

  1. Last updated
  2. Save as PDF
Views:
74
Visibility:
Public
Votes:
0
Category:
netapp_console
Specialty:
ds_cvo
Last Updated:

Applies to

Single node Cloud Volumes Ontap

Issue

Single node CVO upgrade is not getting completed after 2 hours.

Cause

Volume move was running in the background which caused the CVO upgrade to get stuck

Solution

Stop the Volume move and then restart the upgrade.

Partner Notes

partnerNotes_text

Additional Information

additionalInformation_text

Internal Notes

internalNotes_text

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.