Bug 798172 - gluster option server.allow-insecure not being applied dynamically
Summary: gluster option server.allow-insecure not being applied dynamically
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: rpc
Version: 3.2.5
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Rajesh
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-28 08:44 UTC by patrick.allemann
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-28 06:56:45 UTC
Regression: ---
Mount Type: ---
Documentation: DP
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.