Skip to main content
NetApp Knowledge Base

Trident backend configuration fails when FIPS is enabled

  1. Last updated
  2. Save as PDF
Views:
29
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
snapx
Last Updated:

Applies to

  • Astra Trident [Trident]
  • Storage Virtual Machine [SVM]
  • Federal Information Processing Standards [FIPS]
  • TLS 1.3

Issue

  • Backend configuration fails with the following error message:

time="2025-08-01T12:42:10Z" level=error msg="Error creating ONTAP REST API client for initial call. Falling back to ZAPI." crdControllerEvent=add error="Get \"https://SVM_MGMT_LIF_IP/api/cluster?fields=%2A%2A\": context deadline exceeded" logLayer=core requestID=6e586871-1993-45b2-b040-c080cd8c48a3 requestSource=CRD workflow="cr=reconcile"

  • CURL command to the SVM mgmt LIF fails with:

[core@compute0 ~]$ curl -k --user vsadmin -d "<netapp><system-get-version/></netapp>" https://SVM_MGMT_LIF_IP/servlets/netapp.servlets.admin.XMLrequest_filer
Enter host password for user 'vsadmin':
curl: (35) error:1C8000E9:Provider routines::ems not enabled

 

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.