Skip to main content
NetApp Knowledge Base

After increase work node trident pod crash with Reason: CrashLoopBackOff

  1. Last updated
  2. Save as PDF
Views:
250
Visibility:
Public
Votes:
5
Category:
astra_trident
Specialty:
san
Last Updated:

Applies to

  • NetApp Trident
  • Kubernetes (K8s)

Issue

After increase work node trident pod crash with CrashLoopBackOff.

Example:

[root@trident-installer]# kubectl describe pod -n trident
...
State:          Waiting
Reason:       CrashLoopBackOff

From trident-controller-previous-sidecar-csi-attacher  log file find error.

Example:

I0420 11:25:13.495520       1 connection.go:186] GRPC error: rpc error: code = FailedPrecondition desc = Trident initialization failed; 
unable to reconcile node access on backend; error adding IQN iqn.1994-05.com.redhat:18bd666cbf4  
to igroup custom: API status: failed, Reason: Invalid IQN "iqn.1994-05.com.redhat:18bd666cbf4 ": 
The Naming Authority and String fields may contain only the characters a-z, 0-9, ".", ":", and "-"., Code: 13115
E0420 11:25:13.495583       1 main.go:124] CSI driver probe failed: rpc error: code = FailedPrecondition 
desc = Trident initialization failed; unable to reconcile node access on backend; error adding IQN iqn.1994-05.com.redhat:18bd666cbf4
to igroup custom: API status: failed, Reason: Invalid IQN "iqn.1994-05.com.redhat:18bd666cbf4 ": 
The Naming Authority and String fields may contain only the characters a-z, 0-9, ".", ":", and "-"., Code: 13115

 

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.