Skip to main content
NetApp Knowledge Base

Attach PV on NVMe/TCP backend fails by REST API /protocols/nvme/subsystem-maps error

Views:
99
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

  • Astra Trident
  • ONTAP 9.5 and later
  • PV configured on NVMe/TCP backend

Issue

  • Unable to attach PV to pod
  • Command kubectl describe pod <POD> indicates error:

AttachVolume.Attach failed for volume "<PV>" : rpc error: code = Unknown desc = [POST /protocols/nvme/subsystem-maps][409] nvme_subsystem_map_create default  &{Error:0xc000d291d0}

  • trident-controller log also indicates POST /protocols/nvme/subsystem-maps fails

level=error msg="add namespace to subsystem failed, [POST /protocols/nvme/subsystem-maps][409] nvme_subsystem_map_create default  &{Error:0xc0016970e0}" logLayer=core requestID=<REQUESTID> requestSource=CSI workflow="controller=publish"
level=error msg="[POST /protocols/nvme/subsystem-maps][409] nvme_subsystem_map_create default  &{Error:0xc0016970e0}" Method=ControllerPublishVolume Type=CSI_Controller logLayer=csi_frontend requestID=<REQUESTID> requestSource=CSI workflow="controller=publish"
level=error msg="GRPC error: rpc error: code = Unknown desc = [POST /protocols/nvme/subsystem-maps][409] nvme_subsystem_map_create default  &{Error:0xc0016970e0}" logLayer=csi_frontend requestID=<REQUESTID> requestSource=CSI

  • AUDIT-MLOG-TXT.GZ in ONTAP indicates POST /protocols/nvme/subsystem-maps fails because no NVMe LIFs configured on the particular node

POST /api/protocols/nvme/subsystem-maps : ..  :: Error: The node "<NODE>" has no NVMe over Fabrics LIFs configured for SVM "<SVM>".

 

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.