Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

We have had an Equallogic SAN for years and we have been able to connect to it for many months (~6).  All of a sudden this morning at 2:30am our server dropped 2 of the 4 multipath/iscsi sessions that were connected to the SAN.  

In the morning when i went to go take a look it looked like one of the iscsi links failed but in further digging it looks like 2 of the nics decided to change or switch the iqn number to something other than what was authorized by our SAN manufacturer.  

I received the two iqn numbers that my SAN was getting from the redhat machine.  One of them is the one i am using and the other iqn is some random one i have never seen or used before.  I have no idea where it is getting the iqn information from. I checked the nics with iscsiadm -m session -P3 which did show the correct iqn.  I can send more information tomorrow when i have it all but i figured i would write this up.  I have not seen anything online referring to this and I am not sure if this is an issue with Redhat/Hardware/Configuration/San Manufacturer.   Since the SAN manufacturer is seeing two different iqn numbers i am assuming the issue is on my side.

I can post any logs or diagnostics you need.  I didn't want to throw up a bunch of useless information if you didn't need it.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.