Skip to main content
NetApp Knowledge Base

StorageGRID decommision stuck on generating GRID configuration

  1. Last updated
  2. Save as PDF
Views:
319
Visibility:
Public
Votes:
1
Category:
storagegrid-webscale
Specialty:
sgrid
Last Updated:

Applies to

NetApp StorageGRID

Issue

When attempting to resume the decommission operation or update the software of StorageGRID, the following error is observed:
 
500: Internal Server Error
This procedure cannot be started or configured while an existing decommission procedure is in progress.
1 additional copy of this message is not shown
 
 
  • When trying to connect to the Primary Admin node as root, the following errors are shown:
clipboard_e0bab84fc8f6155d0b3df4b600cd7f187.png
 
  • Errors observed within bycast-err.log:
Mar 1 17:02:52 Nodename NMS: |2021-03-01T17:02:52.622| ERROR Unable to connect to Nodename: Unable to connect to <node> on port 22: fingerprint SHA256:4sQQ0VP3+j3XPjOLuEYYN1oYs0kzSciYXo1dFgO9Qfo does not match for "Nodename,IP". Resolve the issue and try again. (MgmtApi::Maintenance::GduClient::Error)

 

 

 

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.