"Hosted engine runs fine on iSCSI since oVirt 3.5.", I have similar configuration and also I have got problem with resolve the hosted-engine storage by vdsm but the cause is that I do know how to edit iSCSI settings. I suspect that there is only one path to target not four :(

Devin what is the output of "hosted-engine --vm-status"?

2017-03-11 16:59 GMT+01:00 Chris Adams <cma@cmadams.net>:
Once upon a time, Devin A. Bougie <devin.bougie@cornell.edu> said:
> Thanks for replying, Juan.  I was under the impression that the hosted engine would run on an iSCSI data domain, based on http://www.ovirt.org/develop/release-management/features/engine/self-hosted-engine-iscsi-support/ and the fact that "hosted-engine --deploy" does give you the option to choose iscsi storage (but only one path, as far as I can tell).

Hosted engine runs fine on iSCSI since oVirt 3.5.  It needs a separate
target from VM storage, but then that access is managed by the hosted
engine HA system.

If all the engine hosts are shut down together, it will take a bit after
boot for the HA system to converge and try to bring the engine back
online (including logging in to the engine iSCSI LUN).  You can force
this on one host by running "hosted-engine --vm-start".

--
Chris Adams <cma@cmadams.net>
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users