Bug 1425288

Summary:	glusterd is not validating for allowed values while setting "cluster.brick-multiplex" property
Product:	[Community] GlusterFS	Reporter:	Gaurav Yadav <gyadav>
Component:	glusterd	Assignee:	Gaurav Yadav <gyadav>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.11.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1438340 (view as bug list)		Environment:
Last Closed:	2017-05-30 18:44:46 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:	1438340

Description Gaurav Yadav 2017-02-21 05:52:09 UTC

Description of problem:
glusterd is not validating for allowed values while setting "cluster.brick-multiplex"  property.
When glusterd set cluster.brick-multiplex property allowed values are on/off, but glusterd gives success message for all combination of string i.e 
gluster v set all cluster.brick-multiplex 12132131
gluster v set all cluster.brick-multiplex ababs

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create a volume
2. gluster v set all cluster.brick-multiplex 12132131

Actual results:
glusterd gives success message for all the values

Expected results:
glusterd should error while setting unknown values.

Additional info:

Comment 1 Atin Mukherjee 2017-02-21 11:40:09 UTC

I don't see any patch posted against this bug, the status should be either in NEW or ASSIGNED.

Comment 2 Worker Ant 2017-02-21 17:53:04 UTC

REVIEW: https://review.gluster.org/16704 (glusterd : cluster.brick-multiplex validation is missing while setting it) posted (#1) for review on master by Gaurav Yadav (gyadav)

Comment 3 Worker Ant 2017-02-22 05:28:14 UTC

REVIEW: https://review.gluster.org/16704 (glusterd : cluster.brick-multiplex validation is missing while setting it) posted (#2) for review on master by Gaurav Yadav (gyadav)

Comment 4 Worker Ant 2017-02-22 05:31:18 UTC

REVIEW: https://review.gluster.org/16704 (glusterd : cluster.brick-multiplex validation is missing while setting it) posted (#3) for review on master by Gaurav Yadav (gyadav)

Comment 5 Worker Ant 2017-02-22 05:42:39 UTC

REVIEW: https://review.gluster.org/16704 (glusterd : cluster.brick-multiplex validation is missing while setting it) posted (#4) for review on master by Gaurav Yadav (gyadav)

Comment 6 Worker Ant 2017-02-22 11:05:59 UTC

COMMIT: https://review.gluster.org/16704 committed in master by Atin Mukherjee (amukherj) 
------
commit 60347526d9611035da0e56d55d4814f51cda9367
Author: Gaurav Yadav <gyadav>
Date:   Tue Feb 21 22:35:47 2017 +0530

    glusterd : cluster.brick-multiplex validation is missing while setting it
    
    Currently glusterd allow setting all values  while setting cluster.brick-multiplex
    option. Validation of allowed options is missing.
    
    With this patch glusterd will validate the values given while setting
    cluster.brick-multiplex.
    
    Change-Id: I938fb16b8f5faa9d31326373cd18632b8aa7ebab
    BUG: 1425288
    Signed-off-by: Gaurav Yadav <gyadav>
    Reviewed-on: https://review.gluster.org/16704
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Atin Mukherjee <amukherj>

Comment 7 Shyamsundar 2017-05-30 18:44:46 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.11.0, please open a new bug report.

glusterfs-3.11.0 has been announced on the Gluster mailinglists [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://lists.gluster.org/pipermail/announce/2017-May/000073.html
[2] https://www.gluster.org/pipermail/gluster-users/