Bug 1773563

Summary:	replicaCount value differs for "volume info" and "volume info --xml" (clone of bug 1773518 )
Product:	[Community] GlusterFS	Reporter:	Omar K <omar.kohl>
Component:	cli	Assignee:	Sanju <srakonde>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, srakonde
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1773518	Environment:
Last Closed:	2020-01-29 07:51:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Omar K 2019-11-18 13:16:10 UTC

+++ This bug was initially created as a clone of Bug #1773518 +++

Description of problem:

The "gluster volume info VOLNAME --xml" differs from the "gluster volume info VOLNAME" output where the replicaCount is concerned. In the first case replicaCount includes the arbiter bricks whereas in the second case it does not.

The correct behaviour should be to exclude the arbiter bricks from replicaCount because that is the way it is done with "gluster volume create" as well.


XML Output:

<brickCount>3</brickCount>
<distCount>3</distCount>
<stripeCount>1</stripeCount>
<replicaCount>3</replicaCount>
<arbiterCount>1</arbiterCount>


regular output:

Number of Bricks: 1 x (2 + 1) = 3

--- Additional comment from Worker Ant on 2019-11-18 10:44:21 UTC ---

REVIEW: https://review.gluster.org/23718 (Exclude arbiter bricks from replicaCount in \"volume info --xml\" output) posted (#1) for review on master by Omar Kohl

Comment 1 Worker Ant 2019-11-18 13:48:21 UTC

REVIEW: https://review.gluster.org/23718 (Exclude arbiter bricks from replicaCount in \"volume info --xml\" output) posted (#2) for review on master by Omar Kohl

Comment 2 Sanju 2020-01-09 08:04:56 UTC

*** Bug 1773518 has been marked as a duplicate of this bug. ***

Comment 3 Sanju 2020-01-29 07:51:08 UTC

As this can break backward compatibility, closing this bug as won't fix.

Thanks,
Sanju