Skip to main content
NetApp Knowledge Base

Trident backends fail with network is unreachable

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

Applies to

  • NetApp Trident 25.02.1
  • NetApp Trident 25.06.2
  • Red Hat OpenShift Container Platform
  • Multus CNI
  • IPv6

Issue

After upgrading Trident from version 25.02.1 to 25.06.2 using customized values and ipv6, all backends fail to initialize with the following error:

FATAL[...] failed to initialize backend: dial tcp [<IPv6>]:443: connect: network is unreachable

  • The same custom YAML worked with Trident 25.02.1.
  • Downgrading back to 25.02.1 restores backend connectivity.
  • The Trident controller pod has no Multus interfaces — only eth0 with a link-local (fe80::/64) address.

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.