Skip to main content
NetApp Knowledge Base

ONTAP update fails to start on two node MetroCluster due to status cluster update waiting

Views:
632
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
metrocluster
Last Updated:

Applies to

  • ONTAP 9
  • MetroCluster

Issue

  • ONTAP update fails to start on two node MetroCluster due to status cluster update waiting
  • The cluster image show-update-progress command indicates that an update is in progress:

Cluster::> cluster image show-update-progress

                                     Estimated         Elapsed
Cluster                               Duration        Duration Status
------------------------------ --------------- --------------- ----------------
Cluster                               01:13:00  238 days 00:12 waiting
Cluster                               01:13:00        00:18:33 completed

Details: Cluster "Cluster" updated successfully.

  • The update cannot be paused, resumed, canceled or aborted:

Cluster::*> cluster image abort-update

Warning: Aborting an update should only be done when an update cannot be
         completed or canceled. This operation may result in a mixed-version in
         this two-node MetroCluster configuration.
         Do you want to continue? {y|n}: y

Error: command failed: entry doesn't exist

 

 

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.