Description of problem: Deployed hosted-engine over FC and tried to add an additional host to the setup using hosted-engine --deploy and picked the LUN that is used by the first host for the HE image. The deployment fails with a dirty storage domain error: [ INFO ] Stage: Setup validation [ ERROR ] Failed to execute stage 'Setup validation': Dirty Storage Domain: Cannot find master domain: 'spUUID=00000000-0000-0000-0000-000000000000, msdUUID=2d33e6a2-8935-4fe0-9868-ff8f38c17ea0' Please clean the storage device and try again Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-1.3.0-0.0.master.20150727115626.git3bf22dc.el7.noarch How reproducible: Always Steps to Reproduce: 1. Deploy hosted-engine over FC 2. Once the setup is running, deploy hosted-engine on a second host that is exposed to the same LUN where the hosted-engine VM is image is located and pick this LUN. Answer 'yes' in the "Is this an additional host setup?" Actual results: Deployment failed with dirty storage error. This is wrong because this is an additional host deployment for an existing setup. It should not try to deploy a new HE image over the LUN. 2015-07-29 12:46:18 DEBUG otopi.context context._executeMethod:155 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 145, in _executeMethod method['method']() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py", line 319, in _validation self._storagePoolConnection() File "/usr/share/ovirt-hosted-engine-setup/scripts/../plugins/ovirt-hosted-engine-setup/storage/storage.py", line 898, in _storagePoolConnection message=status['status']['message'], RuntimeError: Dirty Storage Domain: Cannot find master domain: 'spUUID=00000000-0000-0000-0000-000000000000, msdUUID=2d33e6a2-8935-4fe0-9868-ff8f38c17ea0' Please clean the storage device and try again 2015-07-29 12:46:18 ERROR otopi.context context._executeMethod:164 Failed to execute stage 'Setup validation': Dirty Storage Domain: Cannot find master domain: 'spUUID=00000000-0000-0000-0000-000000000000, msdUUID =2d33e6a2-8935-4fe0-9868-ff8f38c17ea0' Please clean the storage device and try again An attempt to add the same host to the HE setup, to the same cluster where the HE VM is running, only via the webadmin, succeeds. Expected results: Deployment of an additional host on the HE setup using hosted-engine --deploy should work. Additional info: sosreport: http://file.tlv.redhat.com/ebenahar/sosreport-purple-vds2.qa.lab.tlv.redhat.com-20150729125935.tar.xz
Correction: Please ignore: "An attempt to add the same host to the HE setup, to the same cluster where the HE VM is running, only via the webadmin, succeeds." Adding an additional host via the webadmin does make it a hosted-engine host. Therefore, I can't find a workaround.
Occurs also while deploying over iSCSI. Therefore, marking as regression. Logs for iSCSI case: http://file.tlv.redhat.com/ebenahar/sosreport-camel-vdsb.qa.lab.tlv.redhat.com-20150803110508.tar.xz
What is the status on this?
I was able to isolate the issue: with latest VDSM we have a different behavior of prepareImage from NFS to iSCSI. Opening a bug on that and setting as a blocker.
Simone, can you check if 3.5.4 works as expected with regard to this BZ?
Yes, 3.5.4 is not affected.
Additional host deployment over FC succeeded. Host was added successfully to the DC. Verified using: ovirt-hosted-engine-ha-1.3.2.1-1.el7ev.noarch ovirt-hosted-engine-setup-1.3.0-1.el7ev.noarch vdsm-4.17.10.1-0.el7ev.noarch
Since oVirt 3.6.0 has been released, moving from verified to closed current release.