This bug is used for tracking the progress of Gluster 3.8.11. Any fixes that need to get in the release should add "glusterfs-3.8.11" in the "blocks" field of their respective bug.
REVIEW: https://review.gluster.org/17028 (doc : release-notes for GlusterFS-3.8.11) posted (#1) for review on release-3.8 by jiffin tony Thottan (jthottan)
COMMIT: https://review.gluster.org/17028 committed in release-3.8 by jiffin tony Thottan (jthottan) ------ commit 104d07555719cd9c4d8e6b9477f6a3b1e1c14a38 Author: Jiffin Tony Thottan <jthottan> Date: Mon Apr 10 17:36:50 2017 +0530 doc : release-notes for GlusterFS-3.8.11 BUG: 1431410 Change-Id: Iaf1d9603221bc0c70ad1695f5aa0afc2d651d737 Signed-off-by: Jiffin Tony Thottan <jthottan> Reviewed-on: https://review.gluster.org/17028 CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Niels de Vos <ndevos> NetBSD-regression: NetBSD Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org>
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.11, please open a new bug report. glusterfs-3.8.11 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://lists.gluster.org/pipermail/packaging/2017-April/000289.html [2] https://www.gluster.org/pipermail/gluster-users/