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.
Bug 1568572 - iscsiadm discovery command on storage appliance B causes logout from storage appliance A
Summary: iscsiadm discovery command on storage appliance B causes logout from storage ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: iscsi-initiator-utils
Version: 6.9
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Chris Leech
QA Contact: Filip Suba
URL:
Whiteboard:
Depends On:
Blocks: 1414018 1425546
TreeView+ depends on / blocked
 
Reported: 2018-04-17 19:17 UTC by paulp@netapp.com
Modified: 2019-07-03 13:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-03 12:26:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Network trace and iscsi configuration data (669.53 KB, application/x-gzip)
2018-05-31 15:23 UTC, paulp@netapp.com 		no flags Details
View All

Description paulp@netapp.com 2018-04-17 19:17:57 UTC 
Description of problem:
Redhat 6.9 client (also verified happens with 6.6) is lun-booted from network storage device A, so root filesystem is an iscsi device.

Issue discovery command "iscsiadm --mode discovery --type sendtargets --portal <ip address>" to new network storage device B causes Redhat to log out the connection to storage device A.  Then there is a race for the Redhat client to iscsi re-login into device A before some amount of time expires (2 seconds?) and if the login doesn't happen in that time, the root filesystem becomes read-only.

Verified with Wireshark trace the RHEL client chooses to log out of the connection with device A when discovery command is issued with IP address of device B, and then a login operation immediately begins to reestablish the connection with device A.

Since this causes a service disruption I'm looking for a way to prevent the logout from device A when discovering luns on device B.

Version-Release number of selected component (if applicable):
RHEL 6.6 and 6.9

How reproducible:
Readily

Steps to Reproduce:
1. Lun boot RHEL 6.9 using iSCSI lun on network storage device A
2. Issue iscsiadm sendtargets command to network storage device B 
3. Observe iscsi connection to device A is terminated
4. Observe in a high number of instance the iscsi connection is not reestablished fast enough to prevent read-only root filesystem

Actual results:
Root filesystem becomes read-only and the client has to be rebooted.

Expected results:
Iscsi discovery to a storage device does not affect existing iscsi connections.

Additional info:
Comment 2 paulp@netapp.com 2018-05-18 14:10:27 UTC 
Reproduced with RHEL 6.10
Comment 3 Chris Leech 2018-05-22 20:19:21 UTC 
Can you give me more details on the initiator configuration?

Is this with iscsi_tcp or with an iSCSI HBA?
If it's an HBA, which make/driver?
Are the two targets on the same network, or different networks?
Does it reproduce without booting from iSCSI?

Can you share a network trace that shows the logout?
How about the iSCSI configuration from /var/lib/iscsi?

My initial attempts to reproduce this failed, in that I did not see this behavior.
Comment 4 paulp@netapp.com 2018-05-31 15:23:31 UTC 
Created attachment 1446312 [details]
Network trace and iscsi configuration data
Comment 5 paulp@netapp.com 2018-05-31 15:26:07 UTC 
Answering Chris Leech questions:
* This is with iscsi_tcp
* The two targets are on different networks
* I don't have a way to reproduce without booting from iSCSI
* I have attached an attachment with network trace and files from /var/lib/iscsi
Note You need to log in before you can comment on or make changes to this bug.