Bug 1208097 - [SNAPSHOT] : Appending time stamp to snap name while using scheduler to create snapshots should be removed.
Summary: [SNAPSHOT] : Appending time stamp to snap name while using scheduler to creat...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: snapshot
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Avra Sengupta
QA Contact:
URL:
Whiteboard: Scheduler
Depends On:
Blocks: qe_tracker_everglades 1224246
TreeView+ depends on / blocked
 
Reported: 2015-04-01 11:56 UTC by senaik
Modified: 2015-09-01 12:23 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.7.0beta1
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1224246 (view as bug list)
Environment:
Last Closed: 2015-05-14 17:27:14 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description senaik 2015-04-01 11:56:29 UTC
Description of problem:
=======================
Creation of snapshot now by default is created with time stamp unless explicitly specified the option of no-timestamp. 

gluster snapshot create
Usage: snapshot create <snapname> <volname(s)> [no-timestamp] [description <description>] [force]

Currently when using scheduler to create snapshots it appends the time stamp to the snap name which results in the snap name having the time stamp repeat twice. So appending time stamp to snap name while using scheduler to create snapshots should be removed.  


Version-Release number of selected component (if applicable):
============================================================
gluster --version
glusterfs 3.7dev built on Mar 27 2015 01:04:44


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2015-04-02 09:48:29 UTC
REVIEW: http://review.gluster.org/10115 (snapshot/scheduler: Don't append timestamp in scheduled snapshots) posted (#1) for review on master by Avra Sengupta (asengupt)

Comment 2 Anand Avati 2015-04-02 11:05:04 UTC
REVIEW: http://review.gluster.org/10115 (snapshot/scheduler: Don't append timestamp in scheduled snapshots) posted (#2) for review on master by Avra Sengupta (asengupt)

Comment 3 Anand Avati 2015-04-06 10:29:02 UTC
REVIEW: http://review.gluster.org/10115 (snapshot/scheduler: Don't append timestamp in scheduled snapshots) posted (#3) for review on master by Avra Sengupta (asengupt)

Comment 4 Anand Avati 2015-04-06 11:30:45 UTC
REVIEW: http://review.gluster.org/10115 (snapshot/scheduler: Don't append timestamp in scheduled snapshots) posted (#4) for review on master by Avra Sengupta (asengupt)

Comment 5 Anand Avati 2015-04-06 17:22:17 UTC
REVIEW: http://review.gluster.org/10115 (snapshot/scheduler: Don't append timestamp in scheduled snapshots) posted (#5) for review on master by Niels de Vos (ndevos)

Comment 6 Anand Avati 2015-04-07 06:14:31 UTC
REVIEW: http://review.gluster.org/10115 (snapshot/scheduler: Don't append timestamp in scheduled snapshots) posted (#6) for review on master by Rajesh Joseph (rjoseph)

Comment 7 Anand Avati 2015-04-07 13:50:50 UTC
COMMIT: http://review.gluster.org/10115 committed in master by Vijay Bellur (vbellur) 
------
commit 057d2bed4175412e3a95224301eace3e133c1dd3
Author: Avra Sengupta <asengupt>
Date:   Thu Apr 2 15:14:48 2015 +0530

    snapshot/scheduler: Don't append timestamp in scheduled snapshots
    
    The scheduled snapshots will now have names as follows:
    Scheduled-<jobname>-<volume name>.
    
    Stopped appending time-stamp in scheduled snapshots because
    time-stamps are appended in snapshots by default unless
    explicitly asked not to.
    
    Therefore snapshot created from "Job1" of "test_vol" volume
    will look like
    Scheduled-Job1-test_vol_GMT-2015.04.02-09.43.02
    
    Change-Id: I75b4a87d265ed55193f08153fd7ffe521cc5ef68
    BUG: 1208097
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/10115
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Rajesh Joseph <rjoseph>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 8 Niels de Vos 2015-05-14 17:27:14 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.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

Comment 9 Niels de Vos 2015-05-14 17:28:42 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.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

Comment 10 Niels de Vos 2015-05-14 17:35:19 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.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


Note You need to log in before you can comment on or make changes to this bug.