On 04/18/2019 06:24 AM, Matthias Leopold wrote: > Hi, > > the Ceph iSCSI gateway has a problem when receiving discovery auth > requests when discovery auth is not enabled. Target discovery fails in > this case (see below). This is especially annoying with oVirt (KVM > management platform) where you can't separate the two authentication > phases. This leads to a situation where you are forced to use discovery > auth and have the same credentials for target auth (for oVirt target). > These credentials (for discovery auth) would then have to be shared for > other targets on the same gateway, this is not acceptable. I saw that > other iSCSI vendors (FreeNAS) don't have this problem. I don't know if > this is Ceph gateway specific or a general LIO target problem. In any > case I would be very happy if this could be resolved. I think that > smooth integration of Ceph iSCSI gateway and oVirt should be of broader > interest. Please correct me if I got anything wrong. > > kernel messages when discovery_auth is disabled, but auth requests are > received > > Apr 18 13:05:01 ceiscsi0 kernel: CHAP user or password not set for > Initiator ACL > Apr 18 13:05:01 ceiscsi0 kernel: Security negotiation failed. > Apr 18 13:05:01 ceiscsi0 kernel: iSCSI Login negotiation failed. > Incase other people hit this, it can be tracked here: https://github.com/ceph/ceph-iscsi/issues/68 It's a kernel bug where when disabling discovery_auth the kernel was still requiring CHAP. _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |