Skip to main content
NetApp Knowledge Base

Trident worker Nodes Fail to Mount NVMe/TCP Volumes After ONTAP Cluster Expansion

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

Applies to

  • NetApp Trident 25.06 and later
  • ONTAP version 9.15.1 and later
  • Ubuntu 22.04 

Issue

  • After expanding an ONTAP cluster from 2 nodes to 4 nodes and updating Trident backend configuration to include new NVMe/TCP LIFs, Kubernetes worker nodes fail to mount NVMe/TCP volumes provisioned from the new nodes.
  • Volumes are successfully created on ONTAP (Node3/Node4), but the worker nodes do not mount them.
    NVMe connections to new LIFs are not established automatically.
    Trident does not trigger nvme connect to new NVMe/TCP targets after backend update.
  • StatefulSet scaling triggers volume provisioning on new aggregates, but mount fails.

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.