Skip to main content
NetApp Knowledge Base

TRID-19946: Trident Controller CrashLoopBackOff When Backend Has Unreachable Management LIF — Blocks ALL Provisioning

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

Issue

  • When the Trident controller pod restarts (due to OOMKill, node failure, rolling upgrade, or any other reason) and one of the configured backends has a management LIF that is unreachable, the controller enters a permanent CrashLoopBackOff
  • Blocks all storage provisioning, attach, resize, and snapshot operations across all backends, including healthy ones that are fully reachable.
  • Error seen in Trident controller:

           level=error msg="Error creating ONTAP REST API client for initial call. Falling back to               ZAPI." error="Get \https://<IP_address>api/cluster?fields=%2A%2A\: dial tcp                           <IP_address>:443: connect: connection timed out" logLayer=core requestID=xxxx                     requestSource=Internal workflow="core=bootstrap"

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.