Skip to main content
NetApp Knowledge Base

Unable to remove stale entries from failed cluster join attempt

  1. Last updated
  2. Save as PDF
Views:
926
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • Data ONTAP 8.x
  • MDV auditing (mdv_aud) volume
  • SVM/vserver auditing enabled

Issue

After unsuccessful join, a second version of the same node was added to the cluster under a different name. The initial attempt is still showing the previous node as missing and not eligible. Any force unjoin attempts fail with either of the following: 
Error: command failed: [Job 30029] Job failed: Failed to disable cluster-scoped metadata volume support prior to remove-node operation. Reason: [Job 30030] Job failed: An error occurred in the reception and processing of the API reply from the appliance.
Error: command failed: [Job 880010] Job failed: Failed to disable cluster-scoped metadata volume support before remove node operation. Reason: [Job 880011] Job failed: Failed to delete volume

 

 

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.