Import of a data storage domain that has the name of the self hosted engine (hosted_storage by default) will be blocked by the backend.
Since the storage name can be changed in the HE installation, this value is taken from the configuration in case it is different that the default (the option name is HostedEngineStorageDomainName)
Created attachment 972980[details]
screenshot from webadmin, db dump and hosted engine setup logs
Description of problem:
An attempt to import the storage domain which is being used for the hosted-engine image is not blocked by the engine.
I'm reporting this bug so there will be a solution for this flow while using NFS.
https://bugzilla.redhat.com/show_bug.cgi?id=1157243 refers to the iSCSI case.
Version-Release number of selected component (if applicable):
rhev 3.5 vt13.5
How reproducible:
Always
Steps to Reproduce:
1. Deploy hosted-engine (NFS)
2. When the engine is up and running, import a data domain and specify the export path which is used by the hosted engine.
Actual results:
The import operation is allowed, there is no validation if this domain is being used by the hosted engine for the engine image.
proceeding with the import would overwrite the metadata of the storage domain and the setup would be destroyed. (Tried it)
Expected results:
There should be a validation to check if the path holds a storage domain which is used for hosted engine.
Additional info: screenshot from webadmin, db dump and hosted engine setup logs
An attempt to import the hosted engine storage domain while using NFS is now blocked on CanDoAction (the storage domain name is the default):
2015-01-11 14:19:13,994 WARN [org.ovirt.engine.core.bll.storage.AddExistingFileStorageDomainCommand] (ajp-/127.0.0.1:8702-10) [4f60b55d] CanDoAction of action AddExistingFileStorageDomain failed. Reasons:VAR__TYPE__STORAGE__DOMAIN,VAR__ACTION__ADD,ACTION_TYPE_FAILED_HOSTED_ENGINE_STORAGE
Verified using rhev3.5 vt13.6