REVIEW: http://review.gluster.org/9990 (Snapshot: Remove brick details on snapshot create error) posted (#1) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/9999 (Snapshot: Remove brick details on snapshot create error) posted (#1) for review on master by mohammed rafi kc (rkavunga)
REVIEW: http://review.gluster.org/9999 (Snapshot: Remove brick details on snapshot create error) posted (#2) for review on master by mohammed rafi kc (rkavunga)
COMMIT: http://review.gluster.org/9999 committed in master by Vijay Bellur (vbellur) ------ commit e405f6e419387d160f6564d15ad9fd3a43af0d10 Author: Mohammed Rafi KC <rkavunga> Date: Wed Mar 25 15:11:48 2015 +0530 Snapshot: Remove brick details on snapshot create error Since we are not providing complete details of stopped bricks on snapshot create error, it is better to remove the incomplete brick details. BUG: 1205596 Change-Id: I73386059c0d29a6cbe7f2bb6834d8b8fb393db0a Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: http://review.gluster.org/9999 Reviewed-by: Avra Sengupta <asengupt> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
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.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
REVIEW: http://review.gluster.org/11234 (snapshot: Don't print brickdown message multiple times) posted (#2) for review on master by Avra Sengupta (asengupt)
REVIEW: http://review.gluster.org/11234 (snapshot: Don't print failure messages multiple times) posted (#3) for review on master by Avra Sengupta (asengupt)
REVIEW: http://review.gluster.org/11234 (glusterd/mgmt_v3: Print the node info, with failure messages) posted (#4) for review on master by Avra Sengupta (asengupt)
COMMIT: http://review.gluster.org/11234 committed in master by Rajesh Joseph (rjoseph) ------ commit d9e688e42a9b1e4be221fed9c1c85db0c2ae3664 Author: Avra Sengupta <asengupt> Date: Wed Jun 17 14:18:32 2015 +0530 glusterd/mgmt_v3: Print the node info, with failure messages While reporting multiple failure messages from different nodes, print the node ip and the failure stage. Change-Id: I657d3debf1b509e4a27baf9e4b580f1ee32e3c5f BUG: 1205596 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/11234 Reviewed-by: Atin Mukherjee <amukherj> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Rajesh Joseph <rjoseph>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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