Skip to main content
NetApp Knowledge Base

Trident NVMe backend errors with "hostNQN not found"

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

Applies to

  • Trident
  • Kubernetes
  • NVMe/TCP

Issue

Despite having successful manual NVMe connections, attempting to configure nodes for NVMe results in the following trident-controller logs:
 
time="2024-01-25T20:26:19Z" level=error msg="Host NQN is empty" logLayer=core requestID=55e78008-fea0-46ba-ac88-1337deed8b87e requestSource=CSI workflow="controller=publish"
time="2024-01-25T20:26:19Z" level=debug msg="<<<<<< Orchestrator#publishVolume" logLayer=core requestID=55e78008-fea0-46ba-ac88-1337deed8b87e requestSource=CSI workflow="controller=publish"
time="2024-01-25T20:26:19Z" level=error msg="hostNQN not found" Method=ControllerPublishVolume Type=CSI_Controller logLayer=csi_frontend requestID=55e78008-fea0-46ba-ac88-1337deed8b87e requestSource=CSI workflow="controller=publish"
time="2024-01-25T20:26:19Z" level=debug msg="<<<< ControllerPublishVolume" Method=ControllerPublishVolume Type=CSI_Controller logLayer=csi_frontend requestID=55e78008-fea0-46ba-ac88-1337deed8b87e requestSource=CSI workflow="controller=publish"

 

 

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.