Skip to main content
NetApp Knowledge Base

trident-node-linux Pod enters CrashLoopBackOff for minutes after K8s node startup

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

Applies to

  • Trident 25.02 or earlier
  • Kubernetes (K8s) Linux nodes where previously attached ONTAP iSCSI PVs are no longer attached following PV deletion or node drain

Issue

  • The trident-node-linux Pod enters CrashLoopBackOff for minutes after K8s node startup, then stabilizes in the Running state.
  • The trident-main container in the Pod repeatedly logs the following error at intervals of more than 10 seconds:

level=error msg="failed to unstage volume" logLayer=csi_frontend requestID=<REQUEST_ID> requestSource=Internal workflow="plugin=activate"

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.