Skip to main content
NetApp Knowledge Base

Astra Trident pods in CrashLoopBackOff status in an initial installation/deployment

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

Applies to

  • Netapp Astra Trident 
  • RedHat Enterprise Linux (RHEL) 8.6

Issue

In a Trident deployment, several Trident pods got stuck in CrashLoopBackOff status:

kubectl get pods -n trident

NAME                            READY           STATUS        
trident-controller-xxxx-yyy      6/6            Running
trident-node-linux-xyxyx         0/2            CrashLoopBackOff 
trident-node-linux-yzyzx         0/2            CrashLoopBackOff
trident-node-linux-xzxzz         0/2            CrashLoopBackOff
trident-operator-xxxxx-ffff      1/1            Running

 

 

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.