iscsi LUN greater than 255 are not detected
Bug #1915196 reported by
Christophe Drevet-Droguet
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
os-brick |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Due to the way SCSCI present the LUN ID [1], linux introduce a gap after LUN 255. The presented LUN 256 is seen as LUN 16640 by linux. We have to take this into account when probing for the new volume.
So when cinder tells the volume has iSCSI LUN 256, we should check if we see LUN 16640 on the host.
I saw some logic about LUN ID being "< 256" in "os_brick/
tags: | added: iscsi |
To post a comment you must log in.
As far as I know os-brick handles the situation you are describing [1]
[1] https:/ /opendev. org/openstack/ os-brick/ src/branch/ master/ os_brick/ initiator/ linuxscsi. py#L635