Skip to main content
NetApp Knowledge Base

Trident backend is in deleting state blocking existing PV management

  1. Last updated
  2. Save as PDF
Views:
17
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

Trident for Kubernetes & Openshift

Issue

Arriving at a state where one of the trident backends is in "deleting" state on both TBE and TBC level:
  • # kubectl get tbe
        NAME        BACKEND        BACKEND UUID                        
        tbe-8j8ck   tb-ontap-nas   42cd0a0e-a534-4b06-8473-aba8e531e697
  • # kubectl get tbc          
        NAME            BACKEND NAME   BACKEND UUID                           PHASE      STATUS
        tbc-ontap-nas   tb-ontap-nas   42cd0a0e-a534-4b06-8473-aba8e531e697   Deleting   Success
  •  # ./tridentctl get backend  no longer shows the backend.

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.