Bug 1755481 - [ansible e2e] RHHI-V automated deployment fails using cli mode
Summary: [ansible e2e] RHHI-V automated deployment fails using cli mode
Keywords:
Status: CLOSED DUPLICATE of bug 1769382
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhiv-1.6
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: Parth Dhanjal
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1769382
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-25 15:07 UTC by bipin
Modified: 2020-01-21 08:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-21 08:44:03 UTC
Embargoed:


Attachments (Terms of Use)

Description bipin 2019-09-25 15:07:36 UTC
Description of problem:
=======================
While deploying HCI using ansible it fails while running the HE roles. This is seen while deploying via cli method. 

Version-Release number of selected component (if applicable):
=============================================================
RHHI-V 1.6

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

Steps to Reproduce:
===================
1.Follow the Automating RHHI for Virtualization deployment guide
2.The gluster deployment is successfully completed
3.Fails in HE deployment

Actual results:
===============

Expected results:
=================

Additional info:

Comment 6 bipin 2019-09-25 15:24:49 UTC
Just to elaborate, first created the gluster inventory and he_gluster_vars.json file as mentioned in the guide. And then started the deployment using the roles mentioned in hc_deployment.yml. 
'ansible-playbook -i gluster_inventory.yml hc_deployment.yml --extra-vars='@he_gluster_vars.json'

Comment 7 bipin 2019-09-26 05:52:04 UTC
ansible versions used:
======================
ansible-2.8.5-2.el7ae.noarch
ovirt-ansible-engine-setup-1.1.9-1.el7ev.noarch
ovirt-ansible-hosted-engine-setup-1.0.28-1.el7ev.noarch
gluster-ansible-roles-1.0.5-4.el7rhgs.noarch 
gluster-ansible-repositories-1.0.1-1.el7rhgs.noarch 
gluster-ansible-features-1.0.5-3.el7rhgs.noarch 
gluster-ansible-maintenance-1.0.1-1.el7rhgs.noarch 
gluster-ansible-infra-1.0.4-3.el7rhgs.noarch 
gluster-ansible-cluster-1.0-1.el7rhgs.noarch

Comment 8 Sahina Bose 2019-11-14 06:11:05 UTC
Can you take a look if this issue is seen with latest builds too?

Comment 9 Parth Dhanjal 2019-11-14 14:40:12 UTC
(In reply to Sahina Bose from comment #8)
> Can you take a look if this issue is seen with latest builds too?

Sure! I'll check.

Comment 10 SATHEESARAN 2020-01-21 08:44:03 UTC

*** This bug has been marked as a duplicate of bug 1769382 ***


Note You need to log in before you can comment on or make changes to this bug.