After a Lun is mapped in the SAN, RHEV doesn't show the new LUN in the storage domain.
Steps to Reproduce:
1. Map a new LUN in the SAN
2. Open the manager and try to attach the new lun to the storage domain
New Lun isn't showed
New Luns available
Daniel, is this the proper way to add a LUN to the system?
Cesar, can you please add full engine and VDSM logs?
A few questions to identify where the problem lays:
* How the new LUN has been added?
* Which storage server?
* iSCSI or FCP?
* Does the LUN exist in 'multipath -l' output
* Can you try invoke getDeviceList from vdsClient and find the relevant LUN?
Closing due to insufficient data
If this problem still reproduces please reopen and provide relevant fresh logs and requested info