Bug 1773518 - replicaCount value differs for "volume info" and "volume info --xml"
Summary: replicaCount value differs for "volume info" and "volume info --xml"
Keywords:
Status: CLOSED DUPLICATE of bug 1773563
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: 7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Sanju
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-18 10:36 UTC by Omar K
Modified: 2020-01-29 07:52 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
: 1773563 (view as bug list)
Environment:
Last Closed: 2020-01-09 08:04:56 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Omar K 2019-11-18 10:36:46 UTC
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

Comment 1 Worker Ant 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 2 Worker Ant 2019-11-18 13:48:17 UTC
REVISION POSTED: 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 3 Sanju 2020-01-09 08:04:56 UTC
bz #1773563 opened in mainline to track this issue, so closing this bug.

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


Note You need to log in before you can comment on or make changes to this bug.