Skip to main content
NetApp Knowledge Base

Trident iSCSI PVCs Created During ONTAP Node Failover Have Only Single Path After Giveback

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

Applies to

  • Trident 
  • Kubernetes clusters using Trident iSCSI backend
  • Linux Kubernetes worker nodes

Issue

Symptom:

  • When a new PersistentVolumeClaim (PVC) is created during an ONTAP node failover event (such as during an ONTAP upgrade), only one iSCSI path is established for the LUN.
  • After storage giveback (when the node returns to service), multipath is not restored for these PVCs—only a single iSCSI path remains available.
  • This impacts redundancy and may affect application high availability.

Log Output Examples:

  • multipath -ll on affected node shows only a single path for the new LUN.
  • iscsiadm -m session confirms only one active iSCSI session for the PVC/LUN.
  • Trident controller logs during PVC creation: 
    time="2026-07-10T03:36:57Z" level=debug msg="DataLIFs with reporting nodes." logLayer=core reportedDataLIFs="[10.X.X.X]" ...
    (Only one DataLIF listed for affected PVC; two DataLIFs for healthy PVCs.)

Condition:

  • Affects only PVCs created while an ONTAP node is in takeover (failover) state.
  • PVCs created before the upgrade or after full giveback are not affected.
  • Issue persists after giveback; multipath is not restored automatically.

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.