Hide Forgot
Description of problem: ======================= Currently when the snapshot is created without -n (snap name) the command is successful and snapshot is created (system generated name) but the output returns as ??? as snap name [root@snapshot-09 ~]# gluster snapshot create vol-snap0 snapshot create: ???: snap created successfully [root@snapshot-09 ~]# gluster snapshot list vol-snap0 Volume Name : vol-snap0 Number of snaps taken : 1 Number of snaps available : 255 Snap Name : 2013_12_17_01_07_26_732137 Snap Time : 2013-12-17 06:37:27 Snap ID : d2e191ab-aed7-48ff-ab04-8da3eef2fb9f [root@snapshot-09 ~]# When a user doesn't provide a snap name, than CLI generates its own snap name which should be displayed in the return cli when success or failure something similar to: snapshot create: 2013_12_17_01_07_26_732137 : snap created successfully Version-Release number of selected component (if applicable): ============================================================= glusterfs-3.4.0.snap.dec03.2013git-1.el6.x86_64 How reproducible: ================= 1/1 Steps to Reproduce: =================== 1. gluster snapshot create volname Actual results: =============== snapshot create: ???: snap created successfully Expected results: ================= snapshot create: <system generated name> : snap created successfully
Fix at http://review.gluster.org/#/c/6625/
verified with build: glusterfs-3.4.1.snap.jan15.2014git-1.el6.x86_64 snap creation without snap name success and prints the system generated name [root@snapshot-01 ~]# gluster snapshot create vol1 snapshot create: 2014_01_17_05_23_17_123103: snap created successfully [root@snapshot-01 ~]# [root@snapshot-01 ~]# gluster snapshot list vol1 Volume Name : vol1 Number of snaps taken : 1 Number of snaps available : 255 Snap Name : 2014_01_17_05_23_17_123103 Snap Time : 2014-01-17 10:53:18 Snap UUID : 7572bd04-eb96-4fa1-b776-dc841cba55ec [root@snapshot-01 ~]# Marking bug as verified
Marking snapshot BZs to RHS 3.0.
Setting flags required to add BZs to RHS 3.0 Errata
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-1278.html