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 916290 - targetcli: CHAP 2 ways on s390x and ppc64
Summary: targetcli: CHAP 2 ways on s390x and ppc64
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: targetcli
Version: 7.0
Hardware: s390x
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Andy Grover
QA Contact: Bruno Goncalves
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-27 18:21 UTC by Bruno Goncalves
Modified: 2023-03-08 07:25 UTC (History)
1 user (show)

Fixed In Version: kernel-3.9-rc4
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-25 22:41:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Bruno Goncalves 2013-02-27 18:21:27 UTC
Description of problem:
The iSCSI discovery target fails when an s390x target has 2 ways CHAP authentication 
iscsiadm -m discovery -I default -p localhost -t st
iscsiadm: failing authentication, received incorrect CHAP response from target 

iscsiadm: Login authentication failed with target 
iscsiadm: discovery login to ::1 failed, giving up 5
iscsiadm: Could not perform SendTargets discovery: encountered non-retryable iSCSI login failure

Version-Release number of selected component (if applicable):

targetcli-2.0rc1.fb19-1.el7.noarch
3.7.0-0.36.el7.s390x
iscsi-initiator-utils-6.2.0.872-19.el7.s390x

How reproducible:
100%

Steps to Reproduce:
1.Setup targetcli with 1 LUN mapped with 2 ways chap
2.Configure client /etc/iscsi/iscsid.conf to use the same secret
3.run
iscsiadm -m discovery -I default -p localhost -t st

Comment 1 Bruno Goncalves 2013-02-28 12:10:58 UTC
it also reproduced on ppc64

Comment 2 Bill Nottingham 2013-03-15 20:45:51 UTC
Byte ordering?

Comment 3 Andy Grover 2013-03-21 21:46:57 UTC
Yes. Fix accepted upstream but not yet in a released kernel or stable point-release. I'll update again when release versions are known.


Note You need to log in before you can comment on or make changes to this bug.