Description of problem: ------------------------ Ansible playbooks are available to deploy RHHI-V in an unattend-fashion-of deployment. This means all the deployment happens only with command line interface and ansible inventory files + playbooks in place. This was currently in a tech-preview with RHHI-V 1.6. This bug is raised to full qualify this mode of installation to make it generally available for end users to consume for automated installation Version-Release number of selected component (if applicable): -------------------------------------------------------------- RHHI-V 1.7 How reproducible: ------------------ Not applicable Steps to Reproduce: --------------------- Run the automated RHHI-V deployment using ansible inventories and playbooks Expected results: ------------------ RHHI-V deployment should be completed
Tested with RHVH 4.3.8 + RHGS 3.5.1 ( glusterfs-6.0-29.el7rhgs ) with following gluster-ansible packages: 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 RHHI-V deployment end-to-end deployment is successful with the following known_issues 1. Extra vars should be edited Additional var 'he_ansible_host_name' should be removed and memory allocated for Hosted Engine VM ('he_mem_size_MB') should be 16GB (16348MB) Bug: BZ1793398 2. Automated RHHI-V deployment fails for the first time This is a known_issue. Happens due to gluster-eventsapi issue Workaround: Re-attempt the Hosted Engine(HE) deployment alone Bug: BZ1795928 3. Additional hosts are not added to the 'Default' virt cluster with capability to run HE VM Again this becomes a known_issue Workaround: Move the additional hosts to 'maintenance' and reinstall those in RHV Manager UI, with 'HostedEngine=deploy' Bug: BZ1796035
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, 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/RHBA-2020:0508