Skip to main content
NetApp Knowledge Base

Trident second PV SAN deployment fails with igroup already contains initiator

  1. Last updated
  2. Save as PDF
Views:
22
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
SNAPX
Last Updated:

Applies to

  • Trident for Kubernetes and Openshift (25.06.2)
  • ontap-san driver
  • ontap-san-economy driver

Issue

A Trident backend configured with ontap-san fails to deplooy a second LUN to the same node.
The following error message is shown in the trident logs, with a message from ONTAP embedded:
Warning  FailedAttachVolume attachdetach-controller  AttachVolume.Attach failed for volume "pvc-<PV-UUID>" : 
rpc error: code = Unknown desc = error publishing LUN pvc_<PV_UUID>_trident_<BACKEND_PREFIX>_test_pvc_2: 
error adding IQN iqn.2026-01.com.netstal:<HOSTNAME>.[HexCode] to igroup <HOSTNAME>-<BACKEND-UUID>: 
[POST /protocols/san/igroups/{igroup.uuid}/initiators][409] igroup_initiator_create default 
{"error":{"code":"5374035","message":"Initiator group \"<HOSTNAME>-<BACKEND-UUID>\" already contains initiator 
 \"iqn.2026-01.com.netstal:<HOSTNAME>.[hexcode]\".","target":"name"}}

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.