Description of problem: ------------------------ Its highly possible one of the hosts in the RHHI-V cluster may go non-operational, and in those cases users prefer to reprovision the same host fresh post fixing the problems and restore the hosts. This is achieved by the replacing the faulty-previously-existing-node by renewed-itself. This procedure should be available as a playbook, so that the user could perform it with ease Version-Release number of selected component (if applicable): ------------------------------------------------------------- RHHI-V 1.8 How reproducible: ----------------- Not applicable Actual results: ------------------ No easy method to do this process of replacing the host by itself Expected results: ----------------- Easy playbook that replaces the host by itself. Additional info:
Dependent bug is already ON_QA
Tested with RHV 4.4.1 and gluster-ansible-maintenance-1.0.3.el8rhgs There are 2 failures 1. Syntax error related to unremoved "-block" in the role 2. Semantic error, where the 'gluster_ansible_cluster_node' is used to replace host workflow
Tested with gluster-ansible-roles-1.0.5-12.el8rhgs The ansible roles for replacing the host with the host of the same name/FQDN post reprovisioning, is available [root@ ~ ]# ls /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/ | grep node node_prep_inventory.yml node_replace_inventory.yml [root@ ~ ]# ls /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/tasks/ | grep node replace_node.yml
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