Bug 1293309

REVIEW: http://review.gluster.org/13042 (cli/xml: display correct xml output of tier volume) posted (#1) for review on release-3.7 by Gaurav Kumar Garg (ggarg)

REVIEW: http://review.gluster.org/13059 (geo-rep: Fix getting subvol number) posted (#1) for review on release-3.7 by Kotresh HR (khiremat)

REVIEW: http://review.gluster.org/13059 (geo-rep: Fix getting subvol number) posted (#2) for review on release-3.7 by Kotresh HR (khiremat)

REVIEW: http://review.gluster.org/13068 (geo-rep: Fix getting subvol count) posted (#1) for review on release-3.7 by Kotresh HR (khiremat)

COMMIT: http://review.gluster.org/13042 committed in release-3.7 by Dan Lambright (dlambrig) 
------
commit 86fa1507a15eb9e1e4a8e1e83785b5a46eee9aa4
Author: Gaurav Kumar Garg <garg.gaurav52>
Date:   Wed Dec 16 18:04:55 2015 +0530

    cli/xml: display correct xml output of tier volume
    
    This patch is backport of: http://review.gluster.org/#/c/12982/
    
    Currently When hot tier type is distributed-replicate and cold tier
    type is disperse volume then #gluster volume info --xml command is
    not giving its correct output. In case of HOT tier case its displaying
    wrong volume type.
    
    With this fix it will show correct xml output for tier volume
    irrespective of all the type of the volume's.
    
      >> Change-Id: If1de8d52d1e0ef3d0523163abed37b2b571715e8
      >> BUG: 1293309
      >> Signed-off-by: Gaurav Kumar Garg <ggarg>
      >> Reviewed-on: http://review.gluster.org/12982
      >> Tested-by: NetBSD Build System <jenkins.org>
      >> Reviewed-by: mohammed rafi  kc <rkavunga>
      >> Tested-by: Gluster Build System <jenkins.com>
      >> Reviewed-by: Kotresh HR <khiremat>
      >> Reviewed-by: Atin Mukherjee <amukherj>
    
    Change-Id: If1de8d52d1e0ef3d0523163abed37b2b571715e8
    BUG: 1293309
    Signed-off-by: Gaurav Kumar Garg <ggarg>
    (cherry picked from commit b0e126d0edf10946701c2fd4f0f1cf8c7b07eda1)
    Reviewed-on: http://review.gluster.org/13042
    Reviewed-by: hari gowtham <hari.gowtham005>
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Dan Lambright <dlambrig>
    Tested-by: Dan Lambright <dlambrig>

COMMIT: http://review.gluster.org/13059 committed in release-3.7 by Venky Shankar (vshankar) 
------
commit fd26e57537316da736768f32c12058e1e01123ce
Author: Kotresh HR <khiremat>
Date:   Thu Dec 17 12:39:30 2015 +0530

    geo-rep: Fix getting subvol number
    
    Fix getting subvol number if the volume
    type is tier. If the volume type was tier,
    the subvol number was calculated incorrectly
    and hence few of workers didn't become ACTIVE
    resulting in files not being replicated from
    corresponding brick. This patch addresses
    the same.
    
    BUG: 1293309
    Change-Id: I318de346657d330a2394507514bdff61feb92d27
    Signed-off-by: Kotresh HR <khiremat>
    Reviewed-on: http://review.gluster.org/12994
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Aravinda VK <avishwan>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-on: http://review.gluster.org/13059

COMMIT: http://review.gluster.org/13068 committed in release-3.7 by Venky Shankar (vshankar) 
------
commit beca3d718bbb0851ffa0d07199a4779f50d19fdc
Author: Kotresh HR <khiremat>
Date:   Tue Dec 22 12:29:32 2015 +0530

    geo-rep: Fix getting subvol count
    
    Tiering doesn't support disperse volume as hot tier,
    hence xml output doesn't give 'hotdisperseCount'.
    Remove the usage of 'hotdisperseCount' in geo-rep
    and return 0 instead.
    
    BUG: 1293309
    Change-Id: I3f50d21cb51db91e31faebf69af4f72360420b73
    Signed-off-by: Kotresh HR <khiremat>
    Reviewed-on: http://review.gluster.org/13062
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Aravinda VK <avishwan>
    Reviewed-on: http://review.gluster.org/13068

GlusterFS v3.7.8 contains a fix  for this bug, hence closing this bug.

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.7.7, please open a new bug report.

glusterfs-3.7.7 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] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user