REVIEW: http://review.gluster.org/13229 (cli: Add arbiter details to volinfo xml output) posted (#1) for review on master by Ravishankar N (ravishankar)

REVIEW: http://review.gluster.org/13229 (cli: Add arbiter details to volinfo xml output) posted (#2) for review on master by Ravishankar N (ravishankar)

REVIEW: http://review.gluster.org/13229 (cli: Add arbiter details to volinfo xml output) posted (#3) for review on master by Ravishankar N (ravishankar)

REVIEW: http://review.gluster.org/13229 (cli: Add arbiter details to volinfo xml output) posted (#4) for review on master by Ravishankar N (ravishankar)

REVIEW: http://review.gluster.org/13229 (cli: Add arbiter details to volinfo xml output) posted (#5) for review on master by Ravishankar N (ravishankar)

COMMIT: http://review.gluster.org/13229 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit 67b7752eccd8eae6a91f3bc3ff55d65dcf858dc7
Author: Ravishankar N <ravishankar>
Date:   Mon Jan 18 12:19:35 2016 +0530

    cli: Add arbiter details to volinfo xml output
    
    The following are added:
    1. "<arbiterCount>1</arbiterCount>" and
    "<coldarbiterCount>1</coldarbiterCount>"
    
    2. "<isArbiter>0</isArbiter>" on the brick info, like so:
    <brick
    uuid="cafa8612-d7d4-4007-beea-72ae7477f3bb">127.0.0.2:/home/ravi/bricks/brick1
    <name>127.0.0.2:/home/ravi/bricks/brick1</name>
    <hostUuid>cafa8612-d7d4-4007-beea-72ae7477f3bb</hostUuid>
    <isArbiter>0</isArbiter>
    </brick>
    
    Also fix a bug in gluster vol info where the abiter brick was shown the
    wrong brick of the cold tier after performing a tier-attach.
    
    Change-Id: Id978325d02b04f1a08856427827320e169169810
    BUG: 1297750
    Signed-off-by: Ravishankar N <ravishankar>
    Reviewed-on: http://review.gluster.org/13229
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user