Description of problem: The engine does not properly identifies the hosted-engine storage domain with the auto import procedure. Impossible to add additional HA-host. For some reason I don't see that crown is yellow over host that is hosting the engine, its grey, like there is no engine is running on host, although I've added data storage domain already over NFS. I see two hostedengineansible VMs, first one shown as external-hostedengineansible and its down, second shown as hostedengineansible and its up. See photo for more details. Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-2.2.0-0.0.master.20171116111049.gitd675549.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1.Deploy SHE over NFS using hosted-engine --deploy --ansible Actual results: The engine does not properly identifies the hosted-engine storage domain with the auto import procedure. Expected results: Auto import of hosted-engine storage domain should succeed and additional ha-hosts should be added without errors. Additional info: See the attached photo.
Created attachment 1353576 [details] Screenshot from 2016-12-07 15-52-28.png
Created attachment 1353579 [details] sosreport from alma04
Created attachment 1353580 [details] engine log
This is expected, because the origin field change was not implemented yet...
As discussed with Simone, moving back to assigned.
This is only a blocker if Node 0 is the default method for ovirt-4.2.0. Which it is not atm.
The remaining issue is that there is an external VM visible in the VM list right? That is not urgent.
(In reply to Martin Sivák from comment #8) > The remaining issue is that there is an external VM visible in the VM list > right? That is not urgent. The remaining issue is external VM visible and completely failed deployment over FC due to https://bugzilla.redhat.com/show_bug.cgi?id=1455169#c9. This is still no go for the whole RFC, as FC deployment should work just like NFS, iSCSI and Gluster. Please consider for appropriate score and severity.
The whole RFC is in beta status and so this is expected. Also this bug has nothing to do with external VM being visible or FC your issue. I wish you would create a separate bug for the external VM and use the proper bug for the FC issue so we can properly close this one.
(In reply to Martin Sivák from comment #10) > The whole RFC is in beta status and so this is expected. Also this bug has > nothing to do with external VM being visible or FC your issue. I wish you > would create a separate bug for the external VM and use the proper bug for > the FC issue so we can properly close this one. https://bugzilla.redhat.com/show_bug.cgi?id=1527866 had been opened to separate that issue from this bug.
FC issue separated by opening this bug here https://bugzilla.redhat.com/show_bug.cgi?id=1527876
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [No relevant external trackers attached] For more info please contact: infra
Works for me just fine on these components: ovirt-hosted-engine-setup-2.2.7-0.0.master.20180119084226.git3799ea2.el7.centos.noarch ovirt-hosted-engine-ha-2.2.5-0.0.master.20180117160214.20180117160210.gitd5b58a8.el7.centos.noarch ovirt-engine-appliance-4.2-20180121.1.el7.centos.noarch Moving to verified.
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 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.