Bug 1040947

Summary:	[SNAPSHOT] : Snapshot list output displays "Volume <snap_name> Does not exist" which is confusing
Product:	Red Hat Gluster Storage	Reporter:	senaik
Component:	snapshot	Assignee:	Sachin Pandit <spandit>
Status:	CLOSED ERRATA	QA Contact:	senaik
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rhgs-3.0	CC:	nsathyan, rhinduja, rhs-bugs, rjoseph, ssamanta, storage-qa-internal
Target Milestone:	---
Target Release:	RHGS 3.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	SNAPSHOT
Fixed In Version:	3.4.1.snap.jan15.2014	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-22 19:30:15 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:

Description senaik 2013-12-12 11:50:35 UTC

Description of problem:
=======================
While listing snapshot using gluster snapshot list command, it displays  "Volume <snap_name> Does not exist" which is confusing 


Version-Release number of selected component (if applicable):
=============================================================
glusterfs 3.4.0.snap.dec03.2013git

How reproducible:
================
always


Steps to Reproduce:
==================
1.Create a volume and start it 

2.Mount the volume and create snapshot 
 gluster snapshot create volume1 -n SNAP1 -d "this is snap of volume1"
snapshot create: SNAP1: snap created successfully

3.List the snapshot 

gluster snapshot list

Volume Name : volume1
Number of snaps taken : 1
Number of snaps available : 255

	Snap Name : SNAP1
	Snap Time : 2013-12-12 06:09:03
	Snap ID : abc9bd33-6b19-4cd8-b1f7-6b6b7572a1a1
Volume SNAP1 Does not exist

Actual results:
==============
Snapshot list output displays "Volume SNAP1 Does not exist" which is confusing 


Expected results:



Additional info:

Comment 2 Sachin Pandit 2014-01-16 06:16:14 UTC

Till now we were saving the snap info in volume list itself(as snap is also a volume), hence while listing the snapshot it used to show the snap as a volume ( Volume <snap_name> Does not exist ). Now we thought of having a separate list for snaps in order to get rid of the confusion. This issue has been fixed in the patch http://review.gluster.org/#/c/6614/

Comment 3 Rahul Hinduja 2014-01-17 12:34:05 UTC

verified with build: glusterfs-3.4.1.snap.jan15.2014git-1.el6.x86_64

As mentioned in the fix, the snap volumes are not listed by any volume list/info/status command. Because of which the snap volume is not listed as <Volume <snap-name> Does not exist> during the crawl in snap list command.



[root@snapshot-01 ~]# gluster snap list

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

Volume Name                  : vol2
Number of snaps taken        : 2
Number of snaps available    : 254

	Snap Name         : y8
	Snap Time         : 1970-01-01 05:30:00
	Snap UUID         : 25b30e16-09a2-431f-b183-96681f7e70f8

	Snap Name         : y9
	Snap Time         : 1970-01-01 05:30:00
	Snap UUID         : 993b2898-a3f0-4f62-b7e8-7f449260c560

Volume Name                  : vol0
Number of snaps taken        : 11
Number of snaps available    : 245

	Snap Name         : o1
	Snap Time         : 2014-01-17 10:24:34
	Snap UUID         : c30a132a-c13b-414e-940f-45442834013d

	Snap Name         : o2
	Snap Time         : 2014-01-17 10:24:37
	Snap UUID         : 10029202-a4df-4de0-9ddc-18fdaa437adb

	Snap Name         : o3
	Snap Time         : 2014-01-17 10:24:40
	Snap UUID         : c9f7b4a9-2683-471d-8067-6b95f4bd5f77

	Snap Name         : o4
	Snap Time         : 2014-01-17 10:24:43
	Snap UUID         : ffd48dab-f02c-4461-b34a-3b8e2a00ebbd

	Snap Name         : o5
	Snap Time         : 2014-01-17 10:24:46
	Snap UUID         : 0886a452-7aa2-4ae4-86c8-94cbd93c6352

	Snap Name         : o6
	Snap Time         : 2014-01-17 10:24:50
	Snap UUID         : 59f33352-6238-4736-8eb3-934f72ada193

	Snap Name         : o7
	Snap Time         : 2014-01-17 10:24:53
	Snap UUID         : 1c3fb4d2-4dec-408c-8aa1-58fe0009cd5d

	Snap Name         : o8
	Snap Time         : 2014-01-17 10:24:57
	Snap UUID         : 9db07993-0bf2-4398-b1bf-ab91ebe39f9e

	Snap Name         : o9
	Snap Time         : 2014-01-17 10:25:00
	Snap UUID         : 6ce6c74e-c662-4ea6-ba58-6d3fe8be43cf

	Snap Name         : o10
	Snap Time         : 2014-01-17 10:25:04
	Snap UUID         : f6e75a44-bbf2-4808-b4ce-59abdd0085e6

	Snap Name         : 2014_01_17_05_22_39_566750
	Snap Time         : 2014-01-17 10:52:40
	Snap UUID         : 0c480bf8-9328-43a0-aa41-8b24dc95da7a
[root@snapshot-01 ~]# 

[root@snapshot-01 ~]# gluster volume list
vol1
vol2
vol0
[root@snapshot-01 ~]# 


Marking the bug as verified

Comment 5 Nagaprasad Sathyanarayana 2014-04-21 06:18:14 UTC

Marking snapshot BZs to RHS 3.0.

Comment 6 Nagaprasad Sathyanarayana 2014-05-19 10:56:38 UTC

Setting flags required to add BZs to RHS 3.0 Errata

Comment 9 errata-xmlrpc 2014-09-22 19:30:15 UTC

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