> I can't reproduce the issue using FC with an HPE 3PAR array, debugging it I found that the compute node receives a signal after the LUN has been remapped
This makes sense. On fibre channel fabrics, any time a LUN is added or removed an RSCN (https://en.wikipedia.org/wiki/Registered_state_change_notification) is sent out. That should signal to the HBA that it needs to recheck what it has access to, where in this case it will realize that the device it used to have access to is no longer present and trigger the cleanup of the device.
So in this case we are somewhat protected by the storage protocol itself.
> I can't reproduce the issue using FC with an HPE 3PAR array, debugging it I found that the compute node receives a signal after the LUN has been remapped
This makes sense. On fibre channel fabrics, any time a LUN is added or removed an RSCN (https:/ /en.wikipedia. org/wiki/ Registered_ state_change_ notification) is sent out. That should signal to the HBA that it needs to recheck what it has access to, where in this case it will realize that the device it used to have access to is no longer present and trigger the cleanup of the device.
So in this case we are somewhat protected by the storage protocol itself.