Description of problem: Provide ansible role for replacing a GlusterFS node with a new node.
@sahina, we have done work as part of gluster-ansible, need your help in prioritizing.
Ref: https://github.com/sac/gluster-ansible-maintenance
The replace node needs to be tested w.r.t RHHI. Sas/Bipin, do we need a corresponding RHHI bug to track this?
As confirmed with Prajith, approved doc text is Previously, a corrupted {Gluster} peer node was manually reconfigured and was added back to the {Gluster} cluster. In this release, replacing a {Gluster} peer node in a {Gluster} cluster , helps reconfigure {Gluster} and adds the reconfigured node back to the cluster.
Tested with gluster-ansible-maintenance-1.0.1-2.el8rhgs When running the playbook, the gluster peer membership is restored correctly, but the volume restoration is not complete. And for that particular issue, there is a separate bug tracked - https://bugzilla.redhat.com/show_bug.cgi?id=1840003
Upstream PR: https://github.com/gluster/gluster-ansible/pull/108
Tested with gluster-ansible-maintenance-1.0.1-4.el8rhgs and gluster-ansible-roles-1.0.5-12.el8rhgs and RHVH 4.4.1 1. All the playbooks and inventories required for node replacement are available 2. Successfully replace the node with the same host post reinstallation with the same FQDN
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/RHEA-2020:2575