Fun so this appears to be the result of the tgtd backend still being used by Ubuntu based CI hosts. With a Fedora 32 based multinode env I've just deployed using lio-adm I see different WWNs for each volume from a different LVM/iSCSI c-vol backend:
$ ll /dev/disk/by-id/wwn-0x6001405* lrwxrwxrwx. 1 root root 9 Mar 9 13:31 /dev/disk/by-id/wwn-0x600140525061514ba074fd880aac7d00 -> ../../sdb lrwxrwxrwx. 1 root root 9 Mar 9 13:32 /dev/disk/by-id/wwn-0x60014056e6d98ce391f402ea4e6f4e29 -> ../../sdc
I'll rebuild with Focal now and confirm the behaviour with tgtd.
Fun so this appears to be the result of the tgtd backend still being used by Ubuntu based CI hosts. With a Fedora 32 based multinode env I've just deployed using lio-adm I see different WWNs for each volume from a different LVM/iSCSI c-vol backend:
$ ll /dev/disk/ by-id/wwn- 0x6001405* by-id/wwn- 0x6001405250615 14ba074fd880aac 7d00 -> ../../sdb by-id/wwn- 0x60014056e6d98 ce391f402ea4e6f 4e29 -> ../../sdc
lrwxrwxrwx. 1 root root 9 Mar 9 13:31 /dev/disk/
lrwxrwxrwx. 1 root root 9 Mar 9 13:32 /dev/disk/
I'll rebuild with Focal now and confirm the behaviour with tgtd.