Tracker for blockers against release 3.11.1
REVIEW: https://review.gluster.org/17480 (doc: Create release notes for 3.11.1) posted (#1) for review on release-3.11 by Shyamsundar Ranganathan (srangana)
REVIEW: https://review.gluster.org/17480 (doc: Create release notes for 3.11.1) posted (#2) for review on release-3.11 by Shyamsundar Ranganathan (srangana)
REVIEW: https://review.gluster.org/17480 (doc: Create release notes for 3.11.1) posted (#3) for review on release-3.11 by Shyamsundar Ranganathan (srangana)
REVIEW: https://review.gluster.org/17480 (doc: Create release notes for 3.11.1) posted (#4) for review on release-3.11 by Shyamsundar Ranganathan (srangana)
COMMIT: https://review.gluster.org/17480 committed in release-3.11 by Shyamsundar Ranganathan (srangana) ------ commit 8b7aee4f5419552ee4db7a05e8623cee00dd4d2f Author: Shyam <srangana> Date: Tue Jun 6 09:17:30 2017 -0400 doc: Create release notes for 3.11.1 Change-Id: I25988309111494e58bfb00c557262c8702928ab6 BUG: 1456850 Signed-off-by: Shyam <srangana> Reviewed-on: https://review.gluster.org/17480 Smoke: Gluster Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Amar Tumballi <amarts>
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.11.1, please open a new bug report. glusterfs-3.11.1 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/announce/2017-June/000074.html [2] https://www.gluster.org/pipermail/gluster-users/