Skip to main content
NetApp Knowledge Base

Trident Controller Pod Initialization Error Due to Unreachable ONTAP Backend

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

Applies to

Trident

Issue

  • After patching and upgrading a Kubernetes worker node running the Trident controller pod, the controller failed to start. 

level=error msg="Error creating ONTAP REST API client for initial call. Falling back to ZAPI." error="Get \\"https://se23sdata8/api/cluster?fields=**\\": context deadline exceeded" logLayer=core requestID=ee7807ad-46dc-4947-9e2f-1214f372b03e requestSource=Internal workflow="core=bootstrap"

  • Trident controller pod was stuck in initialization.
  • No new volumes could be provisioned.
  • Issue was resolved only after removing the unreachable backend from the Kubernetes/Trident configuration.

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.