Skip to main content
NetApp Knowledge Base

Trident pod in crashloopbackoff status after Trident upgrade

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

Applies to

  • Astra Trident
  • Trident upgrade using Trident operator (Offline mode)
  • OpenShift (OCP)

Issue

After a successful Trident upgrade with no errors, the Trident pod with the container csi-snapshotter is in crashloopbackoff status.

Events:
  Type     Reason   Age                     From   Message
  ----     ------   ----                    ----     -------
  Normal   Pulled   149m (x209 over 19h)    kubelet Container image "<name>/trident/csi-snapshotter:v8.2.1" already present on machine
  Warning  BackOff 4m19s (x5488 over 19h)  kubelet  Back-off restarting failed container csi-snapshotter in pod trident-controller-<name>

oc get pods
NAME                        READY   STATUS             RESTARTS         AGE
trident-controller-   5/6 CrashLoopBackOff   238 (2m5s ago)   19h

Note: The crashloopbackoff status could apply to other containers in a Trident pod.

 

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.