Skip to main content
NetApp Knowledge Base

Multipath devices remain behind after tridenctl volume delete

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

Applies to

Trident for Kubernetes/Openshift

Issue

After manually deleting the PV's ONTAP Volumes using tridentctl volume delete, the multipath mapper devices and disk devices were left behind, causing issues with assigning new LUNs with the same mapping ID. In the multipath -ll output those LUNs can clearly be seen with all paths failed.

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.