Skip to main content
NetApp Knowledge Base

AWS CVOs rebooted twice after an ONTAP upgrade

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

​ ​

Applies to

  • Cloud Volume ONTAP (CVO)
  • OnCommand Cloud Manager (OCCM)
  • Amazon Web Services (AWS)
  • NonDisruptive Upgrade (NDU)

Issue

CVOs rebooted twice after an ONTAP upgrade.

Cause

Takeover initiated on both nodes due to network partitioning in AWS HA soon after a successful upgrade.

[aws-node-01: cf_main: cf.fsm.takeover.netPartition:debug]: Takeover initiated due to network partitioning.

Solution

This is an expected behavior; after a successful NDU, OCCM will shut down the nodes one at a time to take AWS snapshots of system disks.

Additional Information

Add your text here.

 

Internal Notes

BUG 1304437

 

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.