Bug 1635996

Summary: [ansible e2e] HE deployment fails using ansible playbook
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: bipin <bshetty>
Component: rhhiAssignee: Gobinda Das <godas>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: high    
Version: rhhiv-1.5CC: rhs-bugs, sankarshan, sasundar
Target Milestone: ---   
Target Release: RHHI-V 1.5   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: gluster-ansible-roles-1.0.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1636044 (view as bug list) Environment:
Last Closed: 2019-05-20 04:55:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1636044    
Bug Blocks: 1520836    
Attachments:
Description Flags
ansible.log none

Description bipin 2018-10-04 08:14:30 UTC
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

Comment 1 bipin 2018-10-04 08:18:50 UTC
Created attachment 1490407 [details]
ansible.log

Comment 7 Gobinda Das 2018-10-04 10:42:31 UTC
There are some changes happened in hosted-engine role side. I have to test with those changes.

Comment 8 Gobinda Das 2018-10-05 06:00:56 UTC
Raised PR https://github.com/gluster/gluster-ansible/pull/52

Comment 9 SATHEESARAN 2018-10-12 13:15:25 UTC
The dependent gluster-ansible bug is already in MODIFIED state, changing the state of this bug accordingly

Comment 10 SATHEESARAN 2018-10-16 02:47:33 UTC
The dependent gluster-ansible bug is already in ON_QA state, changing the state of this bug

Comment 11 SATHEESARAN 2018-10-16 02:47:48 UTC
Tested with the latest playbook available with gluster-ansible-roles-1.0.3

HC deployment was successful