Bug 1840540

Summary:	Peer restoration logic works only for 3 nodes cluster
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	SATHEESARAN <sasundar>
Component:	gluster-ansible	Assignee:	Prajith <pkesavap>
Status:	CLOSED DUPLICATE	QA Contact:	SATHEESARAN <sasundar>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.5	CC:	rhs-bugs, sabose, sasundar
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-27 08:11:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description SATHEESARAN 2020-05-27 07:41:13 UTC

Description of problem:
------------------------
Existing logic in the gluster-ansible-maintenance roles allows only restoring peers only with 3 nodes cluster. It should be made generic for any numbers of peers in the cluster

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
gluster-ansible-maintenance-1.0.1-2.el8rhgs

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

Steps to Reproduce:
-------------------
1. Execute the role to replace the host

Actual results:
----------------
Peer replacement works only for 3 node gluster cluster

Expected results:
-----------------
Peer replacement should generically work for any number of hosts in the cluster

Additional info:
-----------------
This affects the replace-host workflow

Comment 1 SATHEESARAN 2020-05-27 08:11:39 UTC

Gobinda and I had a discussion to handle this changes as part of the bug https://bugzilla.redhat.com/show_bug.cgi?id=1840003
and there is no need to separate changes.

So CLOSING this bug

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