Bug 732912

Lubos,

can you please try this against rhel6.1GA to see if this is a regression?

Thanks,
Ales

Hi Ales,
For rhel6.1 is it OK, message 'iSCSI login has failed for the following nodes:' is showed for incorrect login.

Indeed, this is a regression, I can reproduce it.

I can reproduce this with iscsiadm, on a rhel6.2 nightly:

[root@parted ~]# iscsiadm -m node
iscsiadm: No records found
[root@parted ~]# iscsiadm -m discovery -t st -p 10.34.39.3
Starting iscsid:                                           [  OK  ]
10.34.39.3:3260,1 iqn.2011-01.com.redhat:cobra03.target1
10.34.39.3:3260,1 iqn.2011-01.com.redhat:cobra03.target2
[root@parted ~]# iscsiadm -m node
10.34.39.3:3260,1 iqn.2011-01.com.redhat:cobra03.target1
10.34.39.3:3260,1 iqn.2011-01.com.redhat:cobra03.target2
[root@parted ~]# iscsiadm -m node -l
Logging in to [iface: default, target: iqn.2011-01.com.redhat:cobra03.target1, portal: 10.34.39.3,3260] (multiple)
Logging in to [iface: default, target: iqn.2011-01.com.redhat:cobra03.target2, portal: 10.34.39.3,3260] (multiple)
Login to [iface: default, target: iqn.2011-01.com.redhat:cobra03.target1, portal: 10.34.39.3,3260] successful.
Login to [iface: default, target: iqn.2011-01.com.redhat:cobra03.target2, portal: 10.34.39.3,3260] successful.
[root@parted ~]# iscsiadm -m session
tcp: [1] 10.34.39.3:3260,1 iqn.2011-01.com.redhat:cobra03.target1
[root@parted ~]# 

Note that it first seemed that we managed to login to iqn.2011-01.com.redhat:cobra03.target2 despite that this target needs a CHAP authentication and no authentication is set in /etc/iscsi/iscsid.conf. The output of calling 'iscsiadm -m session' seems to confirm this. 

Mike, I think this is a regression somewhere in the initiator, on a path common to libiscsi_node_login() and to that what happens when iscsiadm is invoked manually, perhaps just an ignored return value somewhere. This appears in dmesg:

 connection2:0: detected conn error (1020)

Reassigning to iscsi-initiator-utils. If I am getting something wrong then throw it back please.

What target are you using and what CHAP settings did you use for it?

On the initiator side are you setting:

node.session.auth.username
node.session.auth.password

Or 

node.session.auth.username_in
node.session.auth.password_in

Or both?

What about on the target? Are you setting the incoming or outgoing?

(In reply to comment #6)
> What target are you using and what CHAP settings did you use for it?

It's a rhel6 machine with scsi-target-utils-1.0.14-2.el6.x86_64

> On the initiator side are you setting:
> 
> node.session.auth.username
> node.session.auth.password
> 
> Or 
> 
> node.session.auth.username_in
> node.session.auth.password_in

None of those, the lines were commented out.

> What about on the target? Are you setting the incoming or outgoing?

I have this set:

<target iqn.2011-01.com.redhat:cobra03.target1>
    backing-store /var/akozumpl/iscsi-target1
    scsi_sn COBRA03_ISCSI_TARGET_1
    scsi_id COBRA03_ISCSI_TARGET_1_ID
</target>

<target iqn.2011-01.com.redhat:cobra03.target2>
    backing-store /var/akozumpl/iscsi-target2
    incominguser akozumpl anaconda
</target>

Looks like it was just added in 6.2. It is due to some patch that

(In reply to comment #8)
> Looks like it was just added in 6.2. It is due to some patch that

Hit save too soon. I meant to write that it was caused by the patches that added qla4xxx support. Testing a patch now.

This is fixed in iscsi-initiator-utils-6.2.0.872-25.el6.

Reproduced in iscsi-initiator-utils-6.2.0.872-24.el6.x86_64 and verified in iscsi-initiator-utils-6.2.0.872-25.el6.x86_64.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1722.html