Bug 1336100

Summary:	it is not possible to add brick as arbiter
Product:	[Community] GlusterFS	Reporter:	René Pavlík <skyrat>
Component:	arbiter	Assignee:	Ravishankar N <ravishankar>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.7.8	CC:	amukherj, bugs, sarumuga
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-17 12:30:28 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 René Pavlík 2016-05-14 07:57:13 UTC

Description of problem:
It is not possible to add a brick as arbiter to an existing volume in replica setup.

Version-Release number of selected component (if applicable):
3.7.8+

How reproducible:
always

Steps to Reproduce:
1. create replica 2 volume
2. deploy another node to extend the volume
3. there is no way to add the new node as 3rd brick and to act as an arbiter of the new setup

Actual results:
One has to destroy the volume and create a new one in the desired setup with arbiter. One is only able to add the new brick as another full replica node.

Expected results:
the `add-brick` command should accept the arbiter option

Additional info:

Comment 1 Atin Mukherjee 2016-05-14 09:27:33 UTC

The support would be coming in 3.8 release. Please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1318289. A patch http://review.gluster.org/#/c/14126/ is up for review. However the same wouldn't be available in 3.7.x series.

Comment 2 Saravanakumar 2016-05-17 12:30:28 UTC

As mentioned in comment#1, closing this bug.