Bug 1218164

Summary: [SNAPSHOT] : Correction required in output message after initilalising snap_scheduler
Product: [Community] GlusterFS Reporter: senaik
Component: snapshotAssignee: Avra Sengupta <asengupt>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: mainlineCC: amukherj, bugs, gluster-bugs, rjoseph
Target Milestone: ---Keywords: Reopened, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: Scheduler
Fixed In Version: glusterfs-3.8rc2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1224184 1245922 (view as bug list) Environment:
Last Closed: 2016-06-16 12:58:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1186580, 1224184, 1245922    

Description senaik 2015-05-04 10:41:46 UTC 
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:
Comment 1 Anand Avati 2015-08-14 13:03:20 UTC 
REVIEW: http://review.gluster.org/11924 (snapshot/scheduler: Output correction of initialisation) posted (#1) for review on master by Avra Sengupta (asengupt)
Comment 2 Anand Avati 2015-08-19 07:06:43 UTC 
REVIEW: http://review.gluster.org/11924 (snapshot/scheduler: Output correction of initialisation) posted (#2) for review on master by Avra Sengupta (asengupt)
Comment 3 Anand Avati 2015-08-20 06:19:12 UTC 
REVIEW: http://review.gluster.org/11924 (snapshot/scheduler: Output correction of initialisation) posted (#3) for review on master by Avra Sengupta (asengupt)
Comment 4 Anand Avati 2015-08-21 16:43:43 UTC 
REVIEW: http://review.gluster.org/11924 (snapshot/scheduler: Output correction of initialisation) posted (#4) for review on master by Avra Sengupta (asengupt)
Comment 5 Anand Avati 2015-08-24 06:34:40 UTC 
COMMIT: http://review.gluster.org/11924 committed in master by Rajesh Joseph (rjoseph) 
------
commit 6bd770c0314645e5309083b75991b243e54b2838
Author: Avra Sengupta <asengupt>
Date:   Fri Aug 14 18:28:08 2015 +0530

    snapshot/scheduler: Output correction of initialisation
    
    Change-Id: I4a6e00805da7b254b8b08e7bb142960fb6c64923
    BUG: 1218164
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/11924
    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>
Comment 7 Nagaprasad Sathyanarayana 2015-10-25 14:49:10 UTC 
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.
Comment 8 Niels de Vos 2016-06-16 12:58:24 UTC 
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