Bug 1145083 - [SNAPSHOT] : gluster snapshot delete doesnt provide option to delete all / multiple snaps of a given volume
Summary: [SNAPSHOT] : gluster snapshot delete doesnt provide option to delete all / mu...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Sachin Pandit
QA Contact:
URL:
Whiteboard: SNAPSHOT
Depends On: 1048122 1112613
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-22 10:55 UTC by Sachin Pandit
Modified: 2014-11-11 08:39 UTC (History)
10 users (show)

Fixed In Version: glusterfs-3.6.0beta2
Doc Type: Bug Fix
Doc Text:
Clone Of: 1112613
Environment:
Last Closed: 2014-11-11 08:39:39 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2014-09-22 11:33:56 UTC
REVIEW: http://review.gluster.org/8798 (feature/snapshot : Interface to delete all snapshots belonging to a system as-well-as to a particular volume.) posted (#1) for review on release-3.6 by Sachin Pandit (spandit)

Comment 2 Anand Avati 2014-09-22 11:52:21 UTC
REVIEW: http://review.gluster.org/8798 (feature/snapshot : Interface to delete all snapshots belonging to a system as-well-as to a particular volume) posted (#2) for review on release-3.6 by Sachin Pandit (spandit)

Comment 3 Anand Avati 2014-09-23 09:01:08 UTC
COMMIT: http://review.gluster.org/8798 committed in release-3.6 by Vijay Bellur (vbellur) 
------
commit c5aa277ec26cd7cf4109bc8854af50a254edbbd9
Author: Sachin Pandit <spandit>
Date:   Mon Jun 23 09:35:52 2014 +0530

    feature/snapshot : Interface to delete all snapshots belonging to a system as-well-as to a particular volume
    
    Problem :
    With the current design we can only delete a single snapshot.
    And the deletion of volume which contains snapshot is not allowed.
    Because of that user might be forced to delete all the snapshots
    manually before he is allowed to delete a volume.
    
    Solution:
    Following is the interface with which user can delete
    all the snapshots of a system or belonging to a particular volume.
    
            Syntax : gluster snapshot delete all
    
            *To delete all the snapshots present in a system
    
            Syntax : gluster snapshot delete volume <volname>
    
            *To deletes all the snapshot present in a volume specified.
    
    ========================================================================
    Sample Output:
    
    Case 1 : Deleting a single snapshot.
    [root@snapshot-24 glusterfs]# gluster snapshot delete snap1
    Deleting snap will erase all the information about the snap. Do you still want to continue? (y/n) y
    snapshot delete: snap1: snap removed successfully
    
    -----------------------------------------------------------------
    Case 2 : Deleting all the snapshots in a Volume.
    [root@snapshot-24 glusterfs]# gluster snapshot delete volume vol1
    Volume (vol1) contains 9 snapshot(s).
    Do you still want to continue and delete them?  (y/n) y
    snapshot delete: snap2: snap removed successfully
    snapshot delete: snap3: snap removed successfully
    snapshot delete: snap4: snap removed successfully
    snapshot delete: snap5: snap removed successfully
    .
    .
    .
    
    -----------------------------------------------------------------
    Case 3 : Deleting all the snapshots in a system.
    [root@snapshot-24 glusterfs]# gluster snapshot delete all
    System contains 4 snapshot(s).
    Do you still want to continue and delete them?  (y/n) y
    snapshot delete: snap7: snap removed successfully
    snapshot delete: snap8: snap removed successfully
    snapshot delete: snap9: snap removed successfully
    snapshot delete: snap10: snap removed successfully
    ========================================================================
    
    Change-Id: Ifec8e128ab2011cbbba208376b9c92cfbe7d8d71
    BUG: 1145083
    Signed-off-by: Sachin Pandit <spandit>
    Reviewed-on: http://review.gluster.org/8162
    Reviewed-by: Atin Mukherjee <amukherj>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Avra Sengupta <asengupt>
    Reviewed-by: Raghavendra Bhat <raghavendra>
    Reviewed-by: Kaushal M <kaushal>
    Signed-off-by: Sachin Pandit <spandit>
    Reviewed-on: http://review.gluster.org/8798
    Reviewed-by: Vijaikumar Mallikarjuna <vmallika>

Comment 4 Niels de Vos 2014-09-25 08:28:10 UTC
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta2 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018883.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 5 Niels de Vos 2014-11-11 08:39:39 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.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users


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