Description of problem:
======================
While running the HCI deployment using ansible playbook, the HE deployment fails. 
Suspecting the error in the roles defined.


Version-Release number of selected component (if applicable):
============================================================
ovirt-ansible-engine-setup-1.1.0-1.el7ev.noarch
gluster-ansible-roles-1.0.2-2.el7rhgs.noarch

How reproducible:
=================
Always

Steps to Reproduce:
==================
1.Create a playbook to deploy RHHI enviornment
2.Fails while deploying the ovirt-engine-setup 

Actual results:
===============
The ovirt-engine instance fails to start in HostedEngineLocal

Expected results:
================
The service starts and should proceed to the HE deployment

Additional info:
===============
Snippet:

TASK [oVirt.hosted-engine-setup : Wait for ovirt-engine service to start] *****************************************************************************************************************************************
FAILED - RETRYING: Wait for ovirt-engine service to start (30 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (29 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (28 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (27 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (26 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (25 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (24 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (23 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (22 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (21 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (20 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (19 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (18 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (17 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (16 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (15 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (14 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (13 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (12 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (11 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (10 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (9 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (8 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (7 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (6 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (5 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (4 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (3 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (2 retries left).
FAILED - RETRYING: Wait for ovirt-engine service to start (1 retries left).
fatal: [localhost]: FAILED! => {"attempts": 30, "changed": false, "content": "", "msg": "Status code was -1 and not [200]: Request failed: <urlopen error [Errno 113] No route to host>", "redirected": false, "status": -1, "url": "http://hostedenginesm2.lab.eng.blr.redhat.com/ovirt-engine/services/health"}



PS: The deployment via cockpit works fine

--- Additional comment from bipin on 2018-10-04 04:18 EDT ---



--- Additional comment from bipin on 2018-10-04 04:34 EDT ---



--- Additional comment from bipin on 2018-10-04 04:36 EDT ---



--- Additional comment from Red Hat Bugzilla Rules Engine on 2018-10-04 06:34:28 EDT ---

This bug is automatically being provided 'pm_ack+' for the release flag 'rhhi‑2.0', the current release of Red Hat Hyperconverged Infrastructure (RHHI) under active development, having been appropriately marked for the release, and having been provided 'devel_ack+' and 'qa_ack+'

--- Additional comment from Red Hat Bugzilla Rules Engine on 2018-10-04 06:34:28 EDT ---

This BZ is being approved for the RHHI 2.0 release, upon receipt of the 3 ACKs (PM,Devel,QA) for the release flag 'rhhi‑2.0', and having been appropriately marked for the release at the appropriate Tracker BZs

--- Additional comment from Red Hat Bugzilla Rules Engine on 2018-10-04 06:34:28 EDT ---

Since this bug has been approved for the RHHI 2.0 release, through release flag 'rhhi-2.0+', the Target Release is being set to 'RHHI 2.0'