Skip to main content
NetApp Knowledge Base

Trident iSCSI paths do not recover after ONTAP Upgrade

Views:
470
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:
2/28/2025, 2:49:00 PM

Applies to

  • Kubernetes Clusters
  • Trident  23.x until, including 24.10.0
  • iSCSI LUN's

Issue

When an ONTAP storage node is upgraded, that node is taken over by its HA partner and when the ONTAP partner HA node does a failover giveback, some iSCSI storage paths do not recover due to issues on the Kubernetes host side.
 
After the giveback of the ONTAP node, only half of the expected iSCSI paths are seen for some of the LUN's from some of the Kubernetes nodes and Trident logs will show something similar to the below errors:
 
time="2024-11-14T10:29:20Z" level=warning msg="Portal is missing LUN Number(s): [1 2 3 4 5 6 7 8]." CHAPInUse=true logLayer=csi_frontend portal=192.168.1.2 requestID=XXXX-XXX-XXX-XXX-XXXXXXX requestSource=Periodic sessionInfoSource=nodeStage workflow="node_server=heal_iscsi"
time="2024-11-14T10:29:41Z" level=warning msg="Portal is missing LUN Number(s): [6 7 8 9 10 11]." CHAPInUse=true logLayer=csi_frontend portal=192.168.1.3

 

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.