Skip to main content
NetApp Knowledge Base

Trident Controller CrashLoop During Helm Upgrade

  1. Last updated
  2. Save as PDF
Views:
2
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
astra
Last Updated:

Applies to

  • NetApp Trident (Helm deployment)
  • Upgrade from Trident/Helm chart version 100.2606.0 to 100.2606.1
  • Private registry image deployments
  • ONTAP SAN backends

Issue

During an attempted upgrade of NetApp Trident from Helm chart version 100.2606.0 to 100.2606.1, the Trident controller pod entered a CrashLoopBackOff state and failed liveness/readiness probes. Log output included:

level=info msg="Running Trident storage orchestrator." version=26.06.0level=info msg="Activating HTTPS REST frontend." address=":8443"level=error msg="Error creating ONTAP REST API client for initial call. Falling back to ZAPI." error="Get https://<IP>/api/cluster?fields=**: dial tcp <IP>:443: connect: connection timed out"level=error msg="API invocation failed. Post https://<IP>/servlets/netapp.servlets.admin.XMLrequest_filer: context deadline exceeded"level=error msg="error initializing ontap-san driver" error="could not create Data ONTAP API client: error creating ONTAP API client: error reading SVM details: Post https://<IP>/servlets/netapp.servlets.admin.XMLrequest_filer: context deadline exceeded"Warning Unhealthy Readiness probe failed: Error: could not get version: Trident is initializing, please try again later (503 Service Unavailable)Warning BackOff Back-off restarting failed container trident-main in pod trident-controller-xxxxxx_trident

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.