Bug 798172

Summary:	gluster option server.allow-insecure not being applied dynamically
Product:	[Community] GlusterFS	Reporter:	patrick.allemann
Component:	rpc	Assignee:	Rajesh <rajesh>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	3.2.5	CC:	gluster-bugs, vagarwal, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-28 06:56:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	DP	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description patrick.allemann 2012-02-28 08:44:37 UTC

setting the option server.allow-insecure to on requires the volume to be stopped ad re-started. 
The option is set to "off" by default and creates a problem when a client tries to connect:
[rpcsvc.c:962:rpcsvc_handle_rpc_call] glusterd: Request received from non-privileged port. Failing request

The option is being reflected when running gluster volume info but is only applied if the volume is restarted. should be applied dnamically

affects: 3.2.5-1 amd64 on debian.

Comment 1 Rajesh 2012-03-28 06:56:45 UTC

applying this option dynamically will break all existing connection from clients like mounts, gNfs server, glustershd, et al. The expected behaviour is, for new connections, such options must applied, and existing connection should not be interrupted. This applies to 3.3 too, and will be documented.