Bug 1597320

Summary: [Tracking] 'iSCSI Login negotiation failed' messages in logs while draining pods from one node to another
Product: Red Hat Gluster Storage Reporter: Neha Berry <nberry>
Component: gluster-blockAssignee: Prasanna Kumar Kalever <prasanna.kalever>
Status: ASSIGNED --- QA Contact: Rahul Hinduja <rhinduja>
Severity: urgent Docs Contact:
Priority: high    
Version: cns-3.7CC: amark, aos-bugs, aos-storage-staff, bchilds, jsafrane, kramdoss, madam, nberry, pkarampu, pprakash, prasanna.kalever, rcyriac, rhs-bugs, sabose, vbellur, xiubli
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
Few paths are missing for iscsi mpath device. This is because, either CHAP security values mismatch or iscsi CSG: stage 0 has been skipped. Both will result in iSCSI login negotiation to fail. To workaround this issue, delete the app pod which will trigger the restart of the pod. The pod start will then update the credentials and relogins.
Story Points: ---
Clone Of: 1595763 Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1624670, 1624678    
Bug Blocks: 1595763, 1568868, 1622458, 1629847, 1641915, 1642792    

Comment 2 Jan Safranek 2018-07-03 16:47:07 UTC
Unfortunately, OpenShift node does not log iscsiadm commands it runs so I can't check if it tried an authenticated login or not. I can prepare a build with them if this bug is easy enough to reproduce.

In the code I can't see a hole that would allow OpenShift miss authentication in a small fraction of targets.

Comment 40 Bipin Kunal 2018-09-24 10:27:47 UTC
*** Bug 1625824 has been marked as a duplicate of this bug. ***

Comment 42 Prasanna Kumar Kalever 2019-02-07 08:31:54 UTC
*** Bug 1654409 has been marked as a duplicate of this bug. ***

Comment 48 Yaniv Kaul 2019-09-15 14:51:15 UTC
What's the next step here?

Comment 49 Xiubo Li 2019-09-15 23:50:55 UTC
(In reply to Yaniv Kaul from comment #48)
> What's the next step here?

This bug has been fixed in open-iscsi utils, more details could be found in the depending bugzillas [1] and [2].

The fixing PR in open-iscsi utils is [3] and has beed released in iscsi-initiator-utils-6.2.0.874-13.el7.

[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1624670
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=1624678
[3]: https://github.com/open-iscsi/open-iscsi/pull/168


Thanks,