Bug 1098122 - [SNAPSHOT]: Setting greater than allowed snap-max-hard-limit output needs to have space in between
Summary: [SNAPSHOT]: Setting greater than allowed snap-max-hard-limit output needs to ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: mainline
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Sachin Pandit
QA Contact:
URL:
Whiteboard: SNAPSHOT
Depends On: 1083024
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-15 10:53 UTC by Sachin Pandit
Modified: 2015-07-26 22:05 UTC (History)
6 users (show)

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

Attachments (Terms of Use)

Comment 1 Anand Avati 2014-05-15 11:00:58 UTC 
REVIEW: http://review.gluster.org/7777 (cli/snapshot : Dont Do the validation of snapshot config limit in CLI                code path.) posted (#1) for review on master by Sachin Pandit (spandit)
Comment 2 Anand Avati 2014-05-15 12:28:34 UTC 
REVIEW: http://review.gluster.org/7777 (cli/snapshot : Dont Do the validation of snapshot config limit in CLI                code path.) posted (#2) for review on master by Sachin Pandit (spandit)
Comment 3 Anand Avati 2014-06-05 06:30:23 UTC 
COMMIT: http://review.gluster.org/7777 committed in master by Kaushal M (kaushal) 
------
commit 7e3b038c6cea6a89feae684012fa6a33443c7473
Author: Sachin Pandit <spandit>
Date:   Thu May 15 09:24:33 2014 +0530

    cli/snapshot : Dont Do the validation of snapshot config limit in CLI
                   code path.
    
    Problem : If we try to set the volume snap limit to
    more that 256, it always shows value cannot exceed 256,
    irrespective of system max limit.
    
    Solution : Dont do validation in CLI side.
    
    Change-Id: I292c0bc91a1806cd4906fca0151dd98135e6e49a
    BUG: 1098122
    Signed-off-by: Sachin Pandit <spandit>
    Reviewed-on: http://review.gluster.org/7777
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Raghavendra Bhat <raghavendra>
    Reviewed-by: Rajesh Joseph <rjoseph>
    Reviewed-by: Kaushal M <kaushal>
Comment 4 Niels de Vos 2014-09-22 12:40:29 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 5 Niels de Vos 2014-11-11 08:32:40 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.