Bug 1796035 - Automated deployment using ansible roles doesn't deploy additional hosts with hosted-engine capability
Summary: Automated deployment using ansible roles doesn't deploy additional hosts with...
Keywords:
Status: CLOSED ERRATA
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: ---
: RHHI-V 1.8
Assignee: Gobinda Das
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: RHHI-V-1.8-Engineering-Backlog-BZs
TreeView+ depends on / blocked
 
Reported: 2020-01-29 13:11 UTC by SATHEESARAN
Modified: 2020-08-04 14:51 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, additional hosts were not added to the Administrator Portal automatically post deployment. With this release, gluster ansible roles have been updated to ensure that any additional hosts are automatically added to the Administrator Portal
Clone Of:
Environment:
Last Closed: 2020-08-04 14:51:32 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:3314 0 None None None 2020-08-04 14:51:58 UTC

Description SATHEESARAN 2020-01-29 13:11:03 UTC 
Description of problem:
-----------------------
After successful completion of automated deployment of RHHI-V using gluster and ovirt-ansible roles, the additional hosts are added to Virt 'Default' cluster, but those hosts are not added with 'hosted-engine=deploy'

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHVH-4.3.8
gluster-ansible-roles-1.0.5-7.el7rhgs.noarch
gluster-ansible-repositories-1.0.1-1.el7rhgs.noarch
gluster-ansible-maintenance-1.0.1-1.el7rhgs.noarch
gluster-ansible-features-1.0.5-5.el7rhgs.noarch
gluster-ansible-infra-1.0.4-5.el7rhgs.noarch
gluster-ansible-cluster-1.0-1.el7rhgs.noarch
ovirt-ansible-engine-setup-1.1.9-1.el7ev.noarch
ovirt-ansible-repositories-1.1.5-1.el7ev.noarch
ovirt-ansible-hosted-engine-setup-1.0.32-1.el7ev.noarch

How reproducible:
------------------
Always

Steps to Reproduce:
-------------------
1. Complete RHHI-V deployment using gluster-ansible and ovirt-ansible roles
2. Post successful deployment, login in RHV Manager UI
3. Check for hosts added as 'Hosted-Engine=deploy'

Actual results:
---------------
Hosts are added, but not as 'HostedEngine=deploy'

Expected results:
------------------
Hosts should be added with 'HostedEngine=deploy' which makes the host eligible to host Hosted-Engine VM


Additional info:
-----------------
I have put the same inventory file in to /usr/share/ovirt-hosted-engine-setup/gdeploy-inventory.yml but still the hosts are not added as 'HostedEngine=deploy'

But the same playbook is called from cockpit UI. Cockpit RHHI-V deployment works as expected
Comment 3 Sahina Bose 2020-02-06 08:04:56 UTC 
Gobinda, can you check this?
Comment 6 SATHEESARAN 2020-05-13 13:17:53 UTC 
Targeting this bug for RHHI-V 1.8
Comment 7 Gobinda Das 2020-05-13 14:42:57 UTC 
Moving this to ON_QA  to test with latest RHVH-4.4
Comment 8 SATHEESARAN 2020-06-16 03:01:49 UTC 
Verified with RHVH 4.4.1 with gluster-ansible-roles-1.0.5-12.el8rhgs

CLI based RHHI-V deployment using ansible playbooks works to deploy RHHI-V successfully
It takes sometime ( around 10 mins ) for the additional hosts to add up in RHV Manager UI.
Comment 13 errata-xmlrpc 2020-08-04 14:51:32 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (RHHI for Virtualization 1.8 bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:3314
Note You need to log in before you can comment on or make changes to this bug.