Created attachment 1402341 [details] api/storagedomains Description of problem: When there is a master storage domain with name 'data' in the system, and we import another storage domain with name 'data', all succeed and we have two storage domains with name 'data'. Version-Release number of selected component (if applicable): 4.2.1 How reproducible: always Steps to Reproduce: 1. Create master storage domain with name 'data'. 2. Import another storage data domain with name 'data' Actual results: success Expected results: success, but should be possible to activate I guess Additional info:
Ondra, can you please attach the engine logs
Created attachment 1402344 [details] engine.log
I've been trying to reproduce this on my env although I keep getting the same validation message of ACTION_TYPE_FAILED_STORAGE_DOMAIN_NAME_ALREADY_EXIST. Is there any chance you can reproduce this on your env again to know if this is consistent or not?
I managed to reproduce it now. It does reproduce when importing a domain from the GUI without indicating the storage domain name in the textbox
Verified. (Created master storage domain with name 'data' and imported another storage data domain with the same name without indicating the storage domain name in the textbox > Activated the domain > Two storage domains with name 'data'. Is this OK? )
engine - 4.2.2.2-0.1.el7 vdsm - 4.20.19-1.el7ev.x86_64
(In reply to Evelina Shames from comment #5) > Verified. > > (Created master storage domain with name 'data' and imported another storage > data domain with the same name without indicating the storage domain name in > the textbox > Activated the domain > Two storage domains with name 'data'. > Is this OK? ) You should fail and get a CDA message indicating this storage domain name already exists. I see that Lev mentioned that it is fixed In Version: ovirt-engine-4.2.2.4, so could it be that this fix (see [1]) does not exists in 4.2.2.2-0.1.el7 ? [1] https://github.com/oVirt/ovirt-engine/commit/5f1ca1f225c4b991158c782d2d5cb5af832f1cbc
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.