Skip to main content
NetApp Knowledge Base

TRID-20169: Stale VolumeAttachment after unstage of an ontap-san iSCSI volume

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

Issue

  • After a pod that uses an ontap-san ReadWriteOnce iSCSI volume is moved to another node, the new pod can stay in ContainerCreating with a Multi-Attach error.
  • The VolumeAttachment for that volume is still attached to the previous node, so Kubernetes does not attach the volume anywhere else.
  • This shows up when many iSCSI volumes with dm-multipath are unpublished at the same time, for example when a StatefulSet is scaled down and then scaled back up. NAS volumes are not affected

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.