Skip to main content
NetApp Knowledge Base

Trident error 'backend state failed' and unable to see volumes after upgrade to 20.07.1

Views:
747
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
SNAPX
Last Updated:

Applies to

NetApp Trident 20.07.1

Issue

  • After upgrading to Trident (20.07.1), volumes are inaccessible with error: backend state failed
  • Error shown in trident-controller.log:
    time="2020-10-02T14:34:50Z" level=warning msg="K8S helper could not add a storage class: Trident initialization failed;
    error attempting to clean up volume pvc-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX from backend <LIF_NAME>: error destroying volume : API status: failed, Reason: Volume name: The first character must be a letter or underscore., Code:
    13001" name=trident-csi parameters="map[backendType:ontap-nas]" provisioner=csi.trident.netapp.io

 

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.