Skip to main content
NetApp Knowledge Base

Trident ontap-san PVs mounts take a long time or exceed the node attach deadline

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

Applies to

  • Astra Trident (*)
  • ontap-san, ontap-san-economy drivers

Issue

When deploying  ontap-san or ontap-san-economy PVs, each PV can take minutes to come online.
With Trident 25.02.1, which parallelizes the PV creations, the number of PVs requested is of less influence
than the timeouts on the iSCSI LIF connections/logins per iSCSI LUN.
 
The following error messages are found in the Trident node logs:
level=error msg="Error logging in to iSCSI target." error="process killed after timeout"
 
With a large number of SVM iSCSI LIFs, the time can exceed the timeout of Kubernetes for volume attachments:

MountVolume.MountDevice failed for volume "pvc-<UUID>" : rpc error:d desc = context deadline exceeded

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.