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 981320 - iscsiadm: is duplicating iSCSI sessions after reboot
Summary: iscsiadm: is duplicating iSCSI sessions after reboot
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: iscsi-initiator-utils
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Chris Leech
QA Contact: Bruno Goncalves
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-04 13:05 UTC by Bruno Goncalves
Modified: 2023-03-08 07:25 UTC (History)
4 users (show)

Fixed In Version: iscsi-initiator-utils-6.2.0.873-11.el7
Doc Type: Bug Fix
Doc Text:
Cause: NetworkManager event script was restarting the iscsi.service to start sessions configured for automatic startup when new network interfaces came online. But restart was actually tearing down and recreating already active sessions, and races would occur when multiple network interfaces came online in a short period of time, resulting in multiple sessions for a single target configuration. Consequence: Multiple iSCSI session to the same target portal via a single interface were sometimes created. Fix: The NetworkManager event script was changes to use a new reload target of the iscsi.service, which will make attempt to being up sessions that don't exists but will not tear down existing sessions. Result: iSCSI sessions configured for automatic startup should become active once the network is ready, without duplicate sessions.
Clone Of:
Environment:
Last Closed: 2014-06-13 10:39:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Bruno Goncalves 2013-07-04 13:05:43 UTC 
Description of problem:
After rebooting the iSCSI sessions gets duplicated

Version-Release number of selected component (if applicable):
iscsi-initiator-utils-6.2.0.873-7.el7.x86_64 

3.10.0-0.rc7.64.el7.x86_64


How reproducible:
Often (it does not happens always, but most of the time)

Steps to Reproduce:
1.Connect to iSCSI target
iscsiadm -m discovery -I default -p na3170b.lab.bos.redhat.com -t st
10.16.41.222:3260,1 iqn.1992-08.com.netapp:sn.151753773
10.16.43.127:3260,1 iqn.1992-08.com.netapp:sn.151753773

iscsiadm -m node -l
Logging in to [iface: default, target: iqn.1992-08.com.netapp:sn.151753773, portal: 10.16.41.222,3260] (multiple)
Logging in to [iface: default, target: iqn.1992-08.com.netapp:sn.151753773, portal: 10.16.43.127,3260] (multiple)
Login to [iface: default, target: iqn.1992-08.com.netapp:sn.151753773, portal: 10.16.41.222,3260] successful.
Login to [iface: default, target: iqn.1992-08.com.netapp:sn.151753773, portal: 10.16.43.127,3260] successful.

2.There will be 2 sessions (IDs 1 and 2)
3.Rebbot the server

4. Check sessions after reboot
There are 4 sessions.

iscsiadm -m session -P1
Target: iqn.1992-08.com.netapp:sn.151753773
	Current Portal: 10.16.41.222:3260,1
	Persistent Portal: 10.16.41.222:3260,1
		**********
		Interface:
		**********
		Iface Name: default
		Iface Transport: tcp
		Iface Initiatorname: iqn.1994-05.com.redhat:os-reboot
		Iface IPaddress: 10.16.45.84
		Iface HWaddress: <empty>
		Iface Netdev: <empty>
		SID: 1
		iSCSI Connection State: LOGGED IN
		iSCSI Session State: LOGGED_IN
		Internal iscsid Session State: NO CHANGE

		**********
		Interface:
		**********
		Iface Name: default
		Iface Transport: tcp
		Iface Initiatorname: iqn.1994-05.com.redhat:os-reboot
		Iface IPaddress: 10.16.45.84
		Iface HWaddress: <empty>
		Iface Netdev: <empty>
		SID: 3
		iSCSI Connection State: LOGGED IN
		iSCSI Session State: LOGGED_IN
		Internal iscsid Session State: NO CHANGE
	Current Portal: 10.16.43.127:3260,1
	Persistent Portal: 10.16.43.127:3260,1
		**********
		Interface:
		**********
		Iface Name: default
		Iface Transport: tcp
		Iface Initiatorname: iqn.1994-05.com.redhat:os-reboot
		Iface IPaddress: 10.16.45.84
		Iface HWaddress: <empty>
		Iface Netdev: <empty>
		SID: 2
		iSCSI Connection State: LOGGED IN
		iSCSI Session State: LOGGED_IN
		Internal iscsid Session State: NO CHANGE

		**********
		Interface:
		**********
		Iface Name: default
		Iface Transport: tcp
		Iface Initiatorname: iqn.1994-05.com.redhat:os-reboot
		Iface IPaddress: 10.16.45.84
		Iface HWaddress: <empty>
		Iface Netdev: <empty>
		SID: 4
		iSCSI Connection State: LOGGED IN
		iSCSI Session State: LOGGED_IN
		Internal iscsid Session State: NO CHANGE

Actual results:
4 sessions are displayed

Expected results:
The same sessions that existed when server rebooted (2)
Comment 3 Bruno Goncalves 2013-09-04 15:19:06 UTC 
Verified the fix on iscsi-initiator-utils-6.2.0.873-13.el7.x86_64
Comment 4 Ludek Smid 2014-06-13 10:39:44 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.