Description of problem: gluster v set testvol features.uss command accepts invalid random values which are irrelevant. Version-Release number of selected component (if applicable): [root@rhsauto017 yum.repos.d]# rpm -qa | grep glusterfs glusterfs-libs-3.6.0.31-1.el6rhs.x86_64 glusterfs-cli-3.6.0.31-1.el6rhs.x86_64 glusterfs-3.6.0.31-1.el6rhs.x86_64 glusterfs-fuse-3.6.0.31-1.el6rhs.x86_64 glusterfs-server-3.6.0.31-1.el6rhs.x86_64 glusterfs-rdma-3.6.0.31-1.el6rhs.x86_64 samba-glusterfs-3.6.509-169.1.el6rhs.x86_64 glusterfs-api-3.6.0.31-1.el6rhs.x86_64 glusterfs-geo-replication-3.6.0.31-1.el6rhs.x86_64 How reproducible: 100% Steps to Reproduce: 1. [root@rhsauto017 yum.repos.d]# gluster v set testvol features.uss fdhfdlkfadlkf volume set: success 2. [root@rhsauto017 yum.repos.d]# gluster v info Volume Name: testvol Type: Distributed-Replicate Volume ID: 6c43e6df-3981-43eb-b9b2-422616775a49 Status: Started Snap Volume: no Number of Bricks: 2 x 2 = 4 Transport-type: tcp Bricks: Brick1: 10.70.36.247:/rhs/brick1 Brick2: 10.70.36.248:/rhs/brick1 Brick3: 10.70.36.250:/rhs/brick1 Brick4: 10.70.36.251:/rhs/brick1 Options Reconfigured: features.uss: fdhfdlkfadlkf performance.readdir-ahead: on snap-max-hard-limit: 256 snap-max-soft-limit: 90 auto-delete: disable Actual results: gluster command accepts invalid values and gives success message stdout:volume set: success Expected results: gluster command should only accepts valid values like enable or disable Additional info: Document URL: Section Number and Name: Describe the issue: Suggestions for improvement: Additional information:
This bug is identified as a MUST_FIX under 3.0.4 bucket and hence setting the target milestone to 3.0.4.
Providing the qa_ack for this bug as this could be verified within the release timeline
Verified with glusterfs-3.6.0.44-1.el6rhs
Hi Gaurav, The doc text is updated. Please review the same and sign off if it looks ok.
Hi Bhavana, This doc text looks good to me.
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. https://rhn.redhat.com/errata/RHBA-2015-0682.html