REVIEW: http://review.gluster.org/13470 (TIER: avoid reset of ctr-enabled during the issue of gluster v reset) posted (#1) for review on master by hari gowtham (hari.gowtham005)
COMMIT: http://review.gluster.org/13470 committed in master by Jeff Darcy (jdarcy) ------ commit 69af0676c9e55804338abe26b94138da15385747 Author: hari <hgowtham> Date: Thu Feb 18 16:58:28 2016 +0530 TIER: avoid reset of ctr-enabled during the issue of gluster v reset Change-Id: I3f5f29378c8c55cc07a83f5fc1506c4d7e9ac09d BUG: 1309659 Signed-off-by: hari <hgowtham> Reviewed-on: http://review.gluster.org/13470 Smoke: Gluster Build System <jenkins.com> Reviewed-by: Dan Lambright <dlambrig> Tested-by: hari gowtham <hari.gowtham005> CentOS-regression: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Jeff Darcy <jdarcy>
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
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