Skip to main content
NetApp Knowledge Base

Trident Fails to Start After ONTAP Node Failover Due to TLS Certificate Issue

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

Applies to

Trident

Issue

  • Following a node failover event in an ONTAP cluster, Astra Trident installations on two OpenShift clusters failed to start their controller pods.This resulted in downstream issues for Trident node workers and the operator, causing persistent volume claim (PVC) creation and attachment to fail in both staging and production environments.
  • Key log output:

Err: connection error: desc="transport: Error while dialing: dial unix /var/lib/csi/sockets/pluginproxy/csi.sock: connect: no such file or directory"

  • Additionally, running openssl s_client -connect <ONTAP_MGMT_LIF>:443 returned:

error:0A000126:SSL routines:unexpected eof while reading

  • No certificate information was presented, indicating a TLS handshake failure.

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.