Skip to main content
NetApp Knowledge Base

Trident rejects the custom igroup creation

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

Applies to

  • Trident
  • Kuberenetes

Issue

You may encounter a similar error in the trident-controller log:
 
time="2024-04-02T04:49:50Z" level=error msg="unable to update node access rules on backend san-diego; error adding IQN iqn.1994-05.com.redhat:7331cudawuda to igroup custom_igroup_name: error adding IQN iqn.1994-05.com.redhat:7331cudawuda to igroup custom_igroup_name: API status: failed, Reason: You cannot add the node to an initiator group if the node is already present in another initiator group and both initiator groups share a LUN ID, Code: 9140" requestID=58eca252-57c5-4d45-a200-4586a637403f requestSource=CSI

 

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.