[Bugs] [Bug 1218961] New: snapshot: Can not activate the name provided while creating snaps to do any further access

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1218961

            Bug ID: 1218961
           Summary: snapshot: Can not activate the name provided while
                    creating snaps to do any further access
           Product: GlusterFS
           Version: 3.7.0
         Component: snapshot
          Severity: urgent
          Assignee: bugs at gluster.org
          Reporter: vbhat at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
REGRESSION - The snap name provided while creating the snap is pretty much
useless. Because they can't be used to do any further snapshot operations. This
is breaking something which was working earlier. Hence this is a regression.

Version-Release number of selected component (if applicable):
glusterfs-3.7 branch

How reproducible:
Always

Steps to Reproduce:
1. Create a snap with snapname 'snap0'
2. Try to activate the snap with snap0
3. Try to delete the snap with 'snap0'

Actual results:

<bash#> gluster snapshot create snap0 hosdu
snapshot create: success: Snap snap0_GMT-2015.04.30-14.58.30 created
successfully

<bash#> gluster snapshot activate snap0
 Snapshot command failed
 snapshot activate: failed: Snapshot (snap0) does not exist.

Expected results:
I should be able to activate the snapshot using the same name I give.

I am aware of --no-timestamp option, but without that backward compatibility is
broken.

Additional info:

I am aware of the requirement that lead to this change. But that is no reason
to introduce a regression. Backward compatibility must not be broken.


Proposed solution is to provide the access to snaps both by the name as
provided by the user and the name generated by the glusterd. The only thing you
might have to change in snap-scheduler.py is to increment the snap-name each
time a snap is taken. I don't think this is very had thing to do.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.