Description of problem: ======================= Expected range to set the snapshot config snap-max-soft-limit is between 1 -100. But the output mistakenly displays Expected range between 0 - 100. [root@snapshot-09 ~]# gluster snapshot config snap-max-soft-limit 101 Changing snapshot-max-soft-limit will lead to deletion of snapshots if they exceed the new limit. Do you want to continue? (y/n) y Snapshot Config : failed: Invalid snap-max-soft-limit 0. Expected range 0 - 100 Snapshot command failed [root@snapshot-09 ~]# Version-Release number of selected component (if applicable): ============================================================= glusterfs-3.4.1.7.snap.mar27.2014git-1.el6.x86_64 How reproducible: ================= 1/1 Steps to Reproduce: =================== 1. Set the config value to >100 Actual results: =============== [root@snapshot-09 ~]# gluster snapshot config snap-max-soft-limit 101 Changing snapshot-max-soft-limit will lead to deletion of snapshots if they exceed the new limit. Do you want to continue? (y/n) y Snapshot Config : failed: Invalid snap-max-soft-limit 0. Expected range 0 - 100 Snapshot command failed [root@snapshot-09 ~]# Expected results: ================= [root@snapshot-09 ~]# gluster snapshot config snap-max-soft-limit 101 Changing snapshot-max-soft-limit will lead to deletion of snapshots if they exceed the new limit. Do you want to continue? (y/n) y Snapshot Config : failed: Invalid snap-max-soft-limit 0. Expected range 1 - 100 Snapshot command failed [root@snapshot-09 ~]#
Marking snapshot BZs to RHS 3.0.
The patch which fixes this bug can be found in http://review.gluster.org/#/c/7457/
Setting flags required to add BZs to RHS 3.0 Errata
Marking it as dependant of bz 1098093, as there is going to be some changes in the config output message which is not present in the current build.
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. http://rhn.redhat.com/errata/RHEA-2014-1278.html