Bug 1098910 - [SNAPSHOT]: Stale options (Snap volume) needs to be removed from volume info
Summary: [SNAPSHOT]: Stale options (Snap volume) needs to be removed from volume info
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: 3.5.0
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Vijaikumar Mallikarjuna
QA Contact:
URL:
Whiteboard: SNAPSHOT
Depends On: 1098200
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-19 07:40 UTC by Vijaikumar Mallikarjuna
Modified: 2016-05-11 22:47 UTC (History)
6 users (show)

Fixed In Version: glusterfs-3.6.0beta1
Clone Of: 1098200
Environment:
Last Closed: 2014-11-11 08:32:46 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2014-05-19 07:42:08 UTC
REVIEW: http://review.gluster.org/7794 (cli: 'Snapshot Volume: yes/no' for volume info needs to be removed) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)

Comment 2 Anand Avati 2014-05-30 07:00:04 UTC
COMMIT: http://review.gluster.org/7794 committed in master by Krishnan Parthasarathi (kparthas) 
------
commit 7b96fd92de79f367bfa8591becdb30340a4a26e7
Author: Vijaikumar M <vmallika>
Date:   Mon May 19 13:09:07 2014 +0530

    cli: 'Snapshot Volume: yes/no' for volume info needs to be removed
    
    With initial design where the snap volume used to be displayed in
    gluster volume info,
    we used "Snap Volume: yes/on" to distinguish the volume whether its a
    snap volume or the original volume.
    But with new design the snap volumes are not listed in the volume info,
    hence this entry (snap volume:) doesn't make sense to show.
    
    Change-Id: Ic5b9948bf4ef74e89a611742c74a8989cb406866
    BUG: 1098910
    Signed-off-by: Vijaikumar M <vmallika>
    Reviewed-on: http://review.gluster.org/7794
    Reviewed-by: Avra Sengupta <asengupt>
    Reviewed-by: Sachin Pandit <spandit>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Rajesh Joseph <rjoseph>
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Tested-by: Krishnan Parthasarathi <kparthas>

Comment 3 Niels de Vos 2014-09-22 12:40:36 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.0beta1 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/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 4 Niels de Vos 2014-11-11 08:32:46 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.