bin/56728: iscsi redundancy doesn't work

[6bone%6bone.informatik.uni-leipzig.de@localhost]

>Number:         56728
>Category:       bin
>Synopsis:       iscsi redundancy doesn't work
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Feb 22 14:15:00 +0000 2022
>Originator:     Uwe
>Release:        NetBSD 9.99.93
>Organization:
University of Leipizg
>Environment:
NetBSD 6bone.informatik.uni-leipzig.de 9.99.93 NetBSD 9.99.93 (GENERIC)
>Description:
It is not possible to connect an iscsi target redundantly.

If you try the following, the target is only connected via the first send_target:

iscsictl add_send_target -a 172.18.86.130
iscsictl add_send_target -a 172.18.86.131
iscsictl refresh_targets

iscsictl list_targets
     1: iqn.1992-08.com.netapp:naclaug
        2: 172.18.86.130:3260,1026
        3: 172.18.86.131:3260,1027

iscsictl login -P 1

iscsictl list_sessions -c
Session 3: Target iqn.1992-08.com.netapp:naclaug
 Connection 1 Address 172.18.86.130:3260,1026

If the connection to the target is broken, the system will crash a few minutes later.

###########

If you try the following, two connections to the target will be established. However, the system does not seem to recognize that it is the same target.

iscsictl add_send_target -a 172.18.86.130
iscsictl add_send_target -a 172.18.86.131
iscsictl refresh_targets

iscsictl list_targets
     1: iqn.1992-08.com.netapp:naclaug
        2: 172.18.86.130:3260,1026
        3: 172.18.86.131:3260,1027

iscsictl login -P 2
iscsictl login -P 3

iscsictl list_sessions -c
Session 3: Target iqn.1992-08.com.netapp:naclaug
 Connection 1 Address 172.18.86.130:3260,1026
Session 4: Target iqn.1992-08.com.netapp:naclaug
 Connection 1 Address 172.18.86.131:3260,1027

dmesg shows:

[  1643.344321] scsibus4 at iscsi0: 1 target, 16 luns per target
[  1643.344321] sd3 at scsibus4 target 0 lun 11: <NETAPP, LUN C-Mode, 9700> disk fixed
[  1643.344321] sd3: 10240 GB, 65129 cyl, 16 head, 20607 sec, 512 bytes/sect x 21474836480 sectors
[  1643.354566] sd3: GPT GUID: d644c65b-110e-4dd0-9500-0cfc70900463
[  1643.354566] dk0 at sd3: "NetApp01", 21474836413 blocks at 34, type: ffs
[  1643.354566] sd3: async, 8-bit transfers, tagged queueing
[  2057.578810] scsibus5 at iscsi0: 1 target, 16 luns per target
[  2057.588952] sd4 at scsibus5 target 0 lun 11: <NETAPP, LUN C-Mode, 9700> disk fixed
[  2057.588952] sd4: 10240 GB, 65129 cyl, 16 head, 20607 sec, 512 bytes/sect x 21474836480 sectors
[  2057.588952] sd4: GPT GUID: d644c65b-110e-4dd0-9500-0cfc70900463
[  2057.588952] dk1 at sd4: "02203a72-215e-4912-9815-a5025bdd8124", 21474836413 blocks at 34, type: ffs
[  2057.588952] autoconfiguration error: sd4: wedge named 'NetApp01' already existed, using '02203a72-215e-4912-9815-a5025bdd8124'
[  2057.588952] sd4: async, 8-bit transfers, tagged queueing

Unfortunately, the system does not recognize that it is the same target.
>How-To-Repeat:

>Fix: