Maor, Please add steps to reproduce, so the QA can verify this. Thanks!
(In reply to Allon Mureinik from comment #1) > Maor, Please add steps to reproduce, so the QA can verify this. > Thanks! I'm not sure how to reproduce this... I've added a needinfo to add a dependent bug on GetStorageDomainsList failure in VDSM but generally, the QA can "ruin" the GetStorageDomainsList in VDSM before trying to import a Storage Domain (though it will be best to just add the dependent bug if we have it). Tal, is there a dependent bug on this, or can you describe the reproduce steps of how you managed to reproduce this (I think it was related to Gluster FS)?
Discussed face to face, we need to remove an export domain from the system and import it again and this is where the bug reproduced before the fix
I verified this bz with the following scenario using 3.5.1 vt14 1. Created a nfs export domain 2. Moved the nfs export domain to maintenance 3. Detached the nfs export domain 4. Removed the nfs export domain without Formatting it 5. Imported the nfs export domain again - the domain was successfully imported Moving to Verified
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-0888.html