Bug 1145087 - [SNAPSHOT]: error message for invalid snapshot status should be aligned with error messages of info and list
Summary: [SNAPSHOT]: error message for invalid snapshot status should be aligned with ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: 3.6.0
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Sachin Pandit
QA Contact:
URL:
Whiteboard: SNAPSHOT
Depends On: 1117270 1119641
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-22 11:03 UTC by Sachin Pandit
Modified: 2014-11-11 08:39 UTC (History)
6 users (show)

Fixed In Version: glusterfs-3.6.0beta2
Clone Of: 1119641
Environment:
Last Closed: 2014-11-11 08:39:45 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2014-09-22 11:34:06 UTC
REVIEW: http://review.gluster.org/8801 (glusterd: Error msg for snapshot status for no existing snaps should be aligned with error messages of info and list) posted (#1) for review on release-3.6 by Sachin Pandit (spandit)

Comment 2 Anand Avati 2014-09-22 11:51:54 UTC
REVIEW: http://review.gluster.org/8801 (glusterd: Error msg for snapshot status for no existing snaps should be aligned with error messages of info and list.) posted (#2) for review on release-3.6 by Sachin Pandit (spandit)

Comment 3 Anand Avati 2014-09-23 09:01:40 UTC
COMMIT: http://review.gluster.org/8801 committed in release-3.6 by Vijay Bellur (vbellur) 
------
commit 648961865248fac2c8d704bddfc0c78676319d90
Author: Vijaikumar M <vmallika>
Date:   Tue Jul 15 13:49:41 2014 +0530

    glusterd: Error msg for snapshot status for no existing snaps should be aligned with error messages of info and list.
    
    When a snapshot operation like status, info, list
    performed on a non-existing snapshot.
    For Status error message is displayed as 'Snap not found'
    For List and Info error message is displayed as 'Snapshot does not exist'
    Have the consistant error message all the places
    
    Change-Id: I7b241217dba62fda844481731a6858e4ecb12897
    BUG: 1145087
    Signed-off-by: Vijaikumar M <vmallika>
    Reviewed-on: http://review.gluster.org/8309
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Tested-by: Krishnan Parthasarathi <kparthas>
    Signed-off-by: Sachin Pandit <spandit>
    Reviewed-on: http://review.gluster.org/8801
    Tested-by: Gluster Build System <jenkins.com>

Comment 4 Niels de Vos 2014-09-25 08:28:02 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:45 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.