Description of problem:
=======================
When a snapshot status is issued for non existing snap or volume, it fails with error "not found", whereas we use "does not exist" in all the other places.
Output should be consistent across the clis.
Status command output:
=======================
[root@inception ~]# gluster snapshot status snap2
Snapshot Status : failed: Snap (snap2) not found
Snapshot command failed
[root@inception ~]# gluster snapshot status volume vol8
Snapshot Status : failed: Volume (vol8) not found
Snapshot command failed
List command output:
====================
[root@inception ~]# gluster snapshot list snap2
Snapshot list : failed: Volume (snap2) does not exist
Snapshot command failed
[root@inception ~]#
Version-Release number of selected component (if applicable):
==============================================================
glusterfs-3.6.0.24-1.el6rhs.x86_64
How reproducible:
=================
1/1
Steps to Reproduce:
===================
1. gluster snapshot status <non-existing snap>
2. gluster snapshot status volume <non-existing volume>
Additional info:
Comment 2Vijaikumar Mallikarjuna
2014-07-30 09:45:07 UTC
Version : glusterfs-3.7.1-4.el6rhs.x86_64
Changes are made in snapshot status output for a non existant snap and non existant volume as follows :
gluster snapshot status s1
Snapshot Status : failed: Snapshot (s1) does not exist
Snapshot command failed
gluster snapshot status volume v1
Snapshot Status : failed: Volume (v1) does not exist
Snapshot command failed
Marking the bug 'Verified'
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.
https://rhn.redhat.com/errata/RHSA-2015-1495.html