[ClusterLabs] chap lio-t / iscsitarget disabled - why?

[Stefan Friedel]

Hi all,

we've a running drbd - iscsi cluster (two nodes Debian stretch, pacemaker /
corosync, res group w/ ip + iscsitarget/lio-t + iscsiluns + lvm etc. on top of
drbd etc.). Everything is running fine - but we didn't manage to get CHAP to
work. targetcli / lio-t always switches the authentication off after a migration
or restart.

I found the following lines in the iSCSITarget resource file (Debian stretch
/usr/lib/ocf/resource.d/heartbeat/iSCSITarget, also in
https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/iSCSITarget.in):

   [...]
   # TODO: add CHAP authentication support when it gets added back into LIO
   ocf_run targetcli /iscsi/${OCF_RESKEY_iqn}/tpg1/ set attribute authentication=0 || exit $OCF_ERR_GENERIC
   [...]

(l384ff on github).

This targetcli command actually disables authentication...but why? Is the
assumption "LIO does not offer CHAP support" still true? Anybody out there who
is successfully using lio-t + iSCSITarget + CHAP?

Any hint is welcome!

MfG/Sincerely
Stefan Friedel
--
IWR * 4.317 * INF205 * 69120 Heidelberg
T +49 6221 5414404 * F +49 6221 5414427
stefan.friedel at iwr.uni-heidelberg.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20180403/2970b082/attachment.sig>