Skip to main content
NetApp Knowledge Base

Starting Azure maintenance for CVO before the previous one ends skips completion ASUP

  1. Last updated
  2. Save as PDF
Views:
15
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
ds_cvo
Last Updated:

Applies to

  • Cloud Volumes ONTAP (CVO) HA pair
  • Microsoft Azure

Issue

  • The next Azure maintenance events occur as AutoSupport (ASUP) notifications without completion events for the previous ones
  • The number of Azure maintenance events is greater than the number of completion events

Notes:

  • HA Group Notification (USER_TRIGGERED (TEST:MAINT=1h Cloud Provider Maintenance Event. Status: scheduled. Type: freeze. VM: <NODE>.)) NOTICE
  • HA Group Notification (USER_TRIGGERED (TEST:MAINT=END Cloud Provider Maintenance Event. Status: complete.)) NOTICE

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.