This bug is used for tracking the progress of Gluster 3.8.12. Any fixes that need to get in the release should add "glusterfs-3.8.12" in the "blocks" field of their respective bug.
REVIEW: https://review.gluster.org/17252 (doc: release-notes for GlusterFS-3.8.10) posted (#1) for review on release-3.8 by Niels de Vos (ndevos)
REVIEW: https://review.gluster.org/17252 (doc: release-notes for GlusterFS-3.8.12) posted (#2) for review on release-3.8 by Niels de Vos (ndevos)
COMMIT: https://review.gluster.org/17252 committed in release-3.8 by Niels de Vos (ndevos) ------ commit f453425865d7151f27cd43c4c1e96919ec25a4f8 Author: Niels de Vos <ndevos> Date: Thu May 11 12:00:10 2017 +0200 doc: release-notes for GlusterFS-3.8.12 BUG: 1440754 Change-Id: I6602046ddc12834384e11c41a6e8e0cb7a8d5d71 Signed-off-by: Niels de Vos <ndevos> Reviewed-on: https://review.gluster.org/17252 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: jiffin tony Thottan <jthottan> CentOS-regression: 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.12, please open a new bug report. glusterfs-3.8.12 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://lists.gluster.org/pipermail/announce/2017-May/000072.html [2] https://www.gluster.org/pipermail/gluster-users/