Comment 47 for bug 2004555
Revision history for this message
| Gorka Eguileor (gorka) wrote Re: [ussuri] Wrong volume attachment - volumes overlapping when connected through iscsi on host | #47 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Thanks Sean.
Those RSCNs should be the equivalente of the iSCSI AEN messages, that usually trigger the automatic scan of LUNs on the initiator side.
Those aren't happening in OpenStack iSCSI because I added a feature in Open iSCSI that we use os-brick to be able to disable them and only allow manual scans, that way we don't get leftover devices on the compute node when there's a race condition: a volume mapping to that compute happens on Cinder right after a 'volume_disconnect' has happened on that same compute node.
I'll have to check why we haven't seen that situation in FC, because if it's detecting new LUNs and acting on them then we should also get leftover devices
The only explanation I can think of is that maybe in FC the scan is not for all the LUNs but only the LUNs that are currently present in the host.
Simon from Pure is looking to see if he can give me access to a system to double check it also behaves like that.