+++ This bug was initially created as a clone of Bug #1218164 +++ Description of problem: ======================== After initialising snap_scheduler it gives the following message : Successfully inited snapshot scheduler for this node It should be changed to: snap_scheduler.py init snap_scheduler: Successfully initialised snapshot scheduler for this node Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/11925 (snapshot/scheduler: Output correction of initialisation) posted (#1) for review on release-3.7 by Avra Sengupta (asengupt)
COMMIT: http://review.gluster.org/11925 committed in release-3.7 by Rajesh Joseph (rjoseph) ------ commit 8e5fbebc15c94c83c70d7347d8e8624fa164a973 Author: Avra Sengupta <asengupt> Date: Fri Aug 14 18:28:08 2015 +0530 snapshot/scheduler: Output correction of initialisation Backport of http://review.gluster.org/#/c/11924/ Change-Id: I4a6e00805da7b254b8b08e7bb142960fb6c64923 BUG: 1245922 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/11925 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: mohammed rafi kc <rkavunga> Reviewed-by: Rajesh Joseph <rjoseph>
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.4, please open a new bug report. glusterfs-3.7.4 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/12496 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user