Skip to main content
NetApp Knowledge Base

Trident with openshift and NAS-ONTAP fails to create backend

  1. Last updated
    Apr 29, 2025
  2. Save as PDF
Views:
42
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
nas
Last Updated:
4/29/2025, 5:37:42 AM

Applies to

NetApp Trident

Issue

Attempting to connect Trident (running on OpenShift) to a NAS-ONTAP SVM using a generic AD account. The AD team confirms the account is functional, but the connection fails with the following error:

Error: could not create backend: problem initializing storage driver 'ontap-nas': error initializing ontap-nas driver; could not create Data ONTAP API client: error creating ONTAP API client: error reading SVM details: response code 401 (Unauthorized): incorrect or missing credentials (400 Bad Request)

command terminated with exit code 1

Error: exit status 1

 

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.