Skip to main content
NetApp Knowledge Base

Trident - LUN already mapped to initiator(s) in this group error after pod restart

  1. Last updated
    Apr 18, 2025
  2. Save as PDF
Views:
22
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:
4/18/2025, 1:49:43 PM

Applies to

  • Trident
  • ontap-san (iSCSI) backend

Issue

  • Trident is unable to attach a LUN to a Kubernetes worker node due to an ONTAP error, "LUN already mapped to initiator(s) in this group", after a pod is restarted. As the LUN cannot be attached, Kubernetes cannot initialize the pod to bring it online.
  • The pod events and trident-controller logs report the error returned by ONTAP:
time="2025-04-03T12:22:17Z" level=error msg="error publishing ontap-san driver: err not nil, problem mapping LUN /vol/trident_pvc_799d3ab6_6a47_41b9_81b3_64fdc76b06da/lun0: [POST /protocols/san/lun-maps][500] lun_map_create default {\"error\":{\"code\":\"1254223\",\"message\":\"LUN already mapped to initiator(s) in this group\"}}" Method=ControllerPublishVolume Type=CSI_Controller logLayer=csi_frontend requestID=a83ae4fa-11bb-4c58-937a-b7af21223a3c requestSource=CSI workflow="controller=publish"
  • ONTAP shows a duplicate iGroup housing the same initiator as the iGroup the LUN is currently mapped to:
cluster1::*> lun mapping show -igroup node1.k8s-lab.demo.netapp.com-09b5040e-5683-4372-808d-940a2966257c
Vserver    Path                                      Igroup   LUN ID  Protocol
---------- ----------------------------------------  -------  ------  --------
svm1
           /vol/trident_pvc_48908879_cfb4_476f_82fb_9296886a094b/lun0
                                                     node1.k8s-lab.demo.netapp.com-09b5040e-5683-4372-808d-940a2966257c
                                                                   0  iscsi
svm1
           /vol/trident_pvc_799d3ab6_6a47_41b9_81b3_64fdc76b06da/lun0
                                                     node1.k8s-lab.demo.netapp.com-09b5040e-5683-4372-808d-940a2966257c
                                                                   1  iscsi
svm1
           /vol/trident_pvc_81e7155d_dd0f_4008_8762_bbb5ce9d2cea/lun0
                                                     node1.k8s-lab.demo.netapp.com-09b5040e-5683-4372-808d-940a2966257c
                                                                   2  iscsi
3 entries were displayed.
 
cluster1::*> igroup show -vserver svm1 -igroup *k8s-lab*
Vserver   Igroup       Protocol OS Type  Initiators
--------- ------------ -------- -------- ------------------------------------
svm1
node0.k8s-lab.demo.netapp.com-09b5040e-5683-4372-808d-940a2966257c
iscsi    linux    iqn.1994-05.com.redhat:acb129adbbf1
svm1
node1.k8s-lab.demo.netapp.com-09b5040e-5683-4372-808d-940a2966257c
iscsi    linux    iqn.1994-05.com.redhat:e4e11fe8e2d
svm1
node1.k8s-lab.demo.netapp.com-d311fcfc-9235-4f1d-a3db-2100977b17bf
iscsi    linux    iqn.1994-05.com.redhat:e4e11fe8e2d
svm1
node2.k8s-lab.demo.netapp.com-09b5040e-5683-4372-808d-940a2966257c
iscsi    linux    iqn.1994-05.com.redhat:5d6b41eb441b
4 entries were displayed.

 

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.