Bug 1098122
| Summary: | [SNAPSHOT]: Setting greater than allowed snap-max-hard-limit output needs to have space in between | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Sachin Pandit <spandit> |
| Component: | cli | Assignee: | Sachin Pandit <spandit> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | mainline | CC: | bugs, gluster-bugs, nsathyan, rhinduja, spandit, ssamanta |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | SNAPSHOT | ||
| Fixed In Version: | glusterfs-3.6.0beta1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1083024 | Environment: | |
| Last Closed: | 2014-11-11 08:32:40 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: | |
| Embargoed: | |||
| Bug Depends On: | 1083024 | ||
| Bug Blocks: | |||
|
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 (#2) for review on master by Sachin Pandit (spandit) 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> 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/ 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 |