Bug 723294

Summary: Initiaror Fails to reconnect target when the network cable was restoring the connection.
Product: Red Hat Enterprise Linux 6 Reporter: Leichen <clzzzxcvbn>
Component: iscsi-initiator-utilsAssignee: Chris Leech <cleech>
Status: CLOSED WONTFIX QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1CC: coughlan, mchristi
Target Milestone: rc   
Target Release: 6.1   
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: 2017-12-06 11:29:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Leichen 2011-07-19 16:16:04 UTC
Description of problem:
Initiaror Fails to reconnect target when the network cable was restoring the connection.

Version-Release number of selected component (if applicable):
iscsi-initiator-utils-6.2.0.872-21.el6


How reproducible:


Steps to Reproduce:
1.using iscsiadm command to login the target.
2.unplug the ethernet cable between the initiator and target.
3.wait for sereval seconds, insert the ethernet again.
  
Actual results:
the initiaror can not automatic recovery reconnecting .

Expected results:
the initiaror can automatic recovery reconnecting .

Additional info:
When i use the version iscsi-initiator-utils-6.2.0.872-10.el6 ,the problem does not appear, i mean the initiator can automatic reconnecting again.

Comment 2 Mike Christie 2011-07-20 02:28:59 UTC
What target is this with?

Could you send the /var/log/messages?

And could you take a wireshark/tcpdump trace?

And could you send the output of

iscsiadm -m node -T your-target -p ip

and the output of

iscsiadm -m session -P 3

when you have reconnected the cable and when the initiator is not able to reconnect.

And could you send the outpout of ifconfig after you have reconnected the cable?

Comment 3 Leichen 2011-07-20 15:31:12 UTC
(In reply to comment #2)
> What target is this with?
> Could you send the /var/log/messages?
> And could you take a wireshark/tcpdump trace?
> And could you send the output of
> iscsiadm -m node -T your-target -p ip
> and the output of
> iscsiadm -m session -P 3
> when you have reconnected the cable and when the initiator is not able to
> reconnect.
> And could you send the outpout of ifconfig after you have reconnected the
> cable?

yes,i take a tcpdump trace :tcpdump -i ethx -vvv -s 1024 -w a.cap.And use 

wireshark to analyse the "a.cap". I see when the cable restore connection the 

initiator send the command logoff (close session). Normally , the initiator 

should be send login command again to automatic recovery reconnecting .

After i unplug the cable , several seconds later ,i plug the cable ,and i can 

ping succeeful the target ip .

Comment 4 Suzanne Logcher 2011-10-06 18:53:58 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
               
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 5 Mike Christie 2012-03-22 06:49:53 UTC
Is this still a problem for you?

You never sent the iscsiadm outpout and /var/log/messsages I asked for.

Comment 6 Jan Kurik 2017-12-06 11:29:20 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/