Skip to main content
NetApp Knowledge Base

MetroCluster vserver stuck in 'deleting' status

  1. Last updated
    Sep 23, 2021
  2. Save as PDF
Views:
274
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
MetroCluster
Last Updated:
9/23/2021, 1:21:34 PM

Applies to

  • MetroCluster
  • ONTAP 9

Issue

  • After deleting a vserver on the source cluster, the destination ('-mc' vserver) is stuck in a 'deleting' status.
  • There are errors in the MGWD log file
Example:
Mon Aug 30 2021 22:12:07 +02:00 Failed to unconfigure vserver vserver_01-mc Reason: MetroCluster Vserver unconfigure failed for Vserver UUID, Reason: Apply failed for object aclview_ui, Reason: MetroCluster Vserver unconfigure failed for Vserver UUID, Reason: Apply failed for object aclview_ui, Reason: failed to set field "cmddirname" to "volume constituent".
 
  • There are errors in the CRS log file

Example:

Mon Aug 30 2021 22:12:07 +02:00  Apply failed for Object: aclview_ui Method: baseline Row: Table Name: aclview_ui, Operation: get, Fields: vserver_01-mc role-name volume constituent none  Reason: failed to set field "cmddirname" to "volume constituent"

 

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.