[iscsictl] connection to invalid target

[Edward Tomasz Napierała]

On 0629T1458, RA H wrote:
> I have a SAN with four iSCSI targets,
> eui.000B56007135B1B0 through eui.000B56007135B1B3
> 
> I need to validate target names entered manually by a user.
> Normally, I would do this is by searching the output of a discovery
> session. Since iscsictl doesn't allow doing discovery *only*, the only
> way I can think of to validate a target is to connect, then parse the
> output of "iscsictl -L". Unfortunately, attempting to connect to certain
> invalid targets results in connection to a valid target:
> 
> # iscsictl -Ad 192.168.3.111
> # iscsictl -L
> Target name                          Target portal    State
> eui.000B56007135B1B0                 192.168.3.111    Connected: da0
> eui.000B56007135B1B1                 192.168.3.111    Connected: da2
> eui.000B56007135B1B2                 192.168.3.111    Connected: da1
> eui.000B56007135B1B3                 192.168.3.111    Connected: da3
> # iscsictl -Ra
> # iscsictl -A -p 192.168.3.111 -t eui.000B56007135B1A1
> # iscsictl -L
> Target name                          Target portal    State
> eui.000B56007135B1A1                 192.168.3.111    Connected: da0
> # dmesg
> ...
> da0: Serial Number 000B56007135B1B10000
> ...
> 
> As the Serial Number indicates, iscsictl actually connected to
> target eui.000B56007135B1B1.

That's weird.  Could you paste the iscsid debug log when this happens?
(Basically do "pkill iscsid; while :; do iscsid -d; done" in a separate
shell and capture the output).