Skip to main content
NetApp Knowledge Base

Trident NVMe volumes not cleaned up after ingest jobs

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

  • NetApp Trident 26.06 and older
  • NVMe volumes

Issue

  • NVMe volumes managed by Trident are not being cleaned up after GPU-blocking ingest jobs complete.
  • Volumes remain stuck in the 'Released' state or attached to nodes even when hosts show no active NVMe storage.
  • Manual node intervention is required to clean up these volumes.
  • Observed in at least two clusters with node cleanup/ghost attach and controller unpublish failures.
  • No explicit error codes in Trident or ONTAP logs.

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.