Skip to main content
NetApp Knowledge Base

Trident Orchestrator crash looping due to non existing volume

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

Applies to

  • Trident v22.10 and earlier
  • Kubernetes
  • ONTAP 9

Issue

The main trident pod fails initialization with below error
 
Failed to install Trident; err: command terminated with exit code 1;Error: could not get version:
Trident initialization failed;error attempting to clean up volume pvc-XXXX-XXXX from backend Backendname-xxxx:
error checking for existing volume:API status: failed,Reason: Volume name: The first character must be a letter or underscore., Code: 13001 (500 Internal Server Error)

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.