Skip to main content
NetApp Knowledge Base

NVMe queue count selection not possible with Trident

  1. Last updated
  2. Save as PDF
Views:
5
Visibility:
Public
Votes:
0
Category:
not set
Specialty:
not set
Last Updated:

Applies to

  • NetApp AFF-A90 and AFF-C80 nodes
  • NetApp Data ONTAP 9.X
  • NetApp Trident 25.10.0 and 26.06.0
  • OpenShift 4.19.32
  • NVMe/TCP protocol

Issue

  • After adding new ontap nodes AFF-A90 to an exiting ontap cluster, pods fail to mount NVMe/TCP volumes on the new  nodes, using Trident
  • Pod events show errors:

    MountVolume.MountDevice failed for volume "pvc-yyyyzzzz-xxxx-yyyy-zzzz-xyxyxyxyxy": rpc error: code=Internal desc=failed to stage volume: failed to connect subsystem nqn.1992-08.com.netapp:sn.zzzzzzzz-yyyy-xxxx-yxyx-xyxyxyxyxyxy:subsystem.hostname-xxxxxxx-yyyy to XX.YY.ZZ.YY; exit status 1; failed to connect subsystem nqn.1992-08.com.netapp:sn.zzzzzzzz-yyyy-xxxx-yxyx-xyxyxyxyxyxy:subsystem.hostname-xxxxxxx-yyyy

  • Trident logs show:

    Failed to get subsystem: no subsystem paths found; returning minimal subsystem Error="no subsystem paths found"
    could not add new controller: failed to write to nvme-fabrics device
  • Customer observed that NVMe connections succeed on AFF-C80 (2 queues), but fail on AFF-A90 (4 queues)
  • NVMe/TCP mount failures occur with default queue count of 4 on AFF-A90

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.