Bug 1404095

Summary: Different iscsi IQNs on same host.
Product: Red Hat Enterprise Linux 7 Reporter: Brad Breitenstein <brad.breitenstein>
Component: iscsi-initiator-utilsAssignee: Chris Leech <cleech>
Status: CLOSED WONTFIX QA Contact: Martin Hoyer <mhoyer>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.2   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-01-15 07:29:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Brad Breitenstein 2016-12-13 03:18:16 UTC 
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.
Comment 2 Brad Breitenstein 2016-12-13 22:16:14 UTC 
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.
Comment 6 RHEL Program Management 2021-01-15 07:29:10 UTC 
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.