Bug 1133567

Summary:	Volume option set <vol> <key> <value> command input not consistent
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Marcel Hergaarden <mhergaar>
Component:	glusterd	Assignee:	Satish Mohan <smohan>
Status:	CLOSED WONTFIX	QA Contact:	SATHEESARAN <sasundar>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.0	CC:	amukherj, kaushal, nlevinki, rhs-bugs, sasundar, smohan, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1140628 (view as bug list)		Environment:
Last Closed:	2017-08-11 10:02:58 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:
Bug Blocks:	1140628

Description Marcel Hergaarden 2014-08-25 13:22:18 UTC

Description of problem:
Setting features by using the "volume option set" cmd is not always consistent.
In some cases it will take any given input while in other cases boolean values are to be accepted only.

example 1: gluster volume set <vol> nfs.disable fun
(Will report back: "fun" is not a valid boolean value)

example 2: gluster volume set <vol> features.uss type_whatever
(will report back: "volume set: success")

If you now ask volume status on <vol>, it will actually show:
"deatures.uss: type_whatever"

Version-Release number of selected component (if applicable):
RHS3.0 (using: RHSS-3.0-20140805.0-RHS-x86_64-DVD1.iso)

How reproducible:
Install RHS 3.0 (Denali), create vol and set certain volume options using any other value then ON|OFF or ENABLE|DISABLE.


Steps to Reproduce:
1.Install RHS
2.Create volume
3.Set volume option using any fictional option
4.System will accept fake option without any rejection

Actual results:
Accepts any given option (whilst using i.e. features.uss option, among others)
and will show the fake option while querying volume status

Expected results:
Denial of any other option then on|off or enable|disable as boolean values

Additional info:
This is true for several options, where others behave like expected.
Notices this behavior for the following options while testing;

- features.uss
- rpc.auth allow

Comment 2 SATHEESARAN 2014-08-26 07:32:50 UTC

Marking the appropriate component under  glusterfs-server.
Also defining the severity as MEDIUM, as uss is in TP state.