Bug 1009716 - Need a gluster command to add "option rpc-auth-allow-insecure on" in /etc/glusterfs/glusterd.vol file
Summary: Need a gluster command to add "option rpc-auth-allow-insecure on" in /etc/gl...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd
Version: 2.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: Lalatendu Mohanty
URL:
Whiteboard: glusterd
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-19 01:31 UTC by Lalatendu Mohanty
Modified: 2018-04-01 05:02 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-01 05:02:15 UTC
Target Upstream Version:

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

Description Lalatendu Mohanty 2013-09-19 01:31:14 UTC 
Description of problem:

Need a gluster command to add "option rpc-auth-allow-insecure on" in  /etc/glusterfs/glusterd.vol file for all rhs nodes

Currently we are suggesting customers to manually edit /etc/glusterfs/glusterd.vol file in each node to put "option rpc-auth-allow-insecure on" which be which is a difficult thing to do when we have more nodes e.g. 30 rhs nodes. 

There should be a gluster command which should do it, when executed from any one node.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Vivek Agarwal 2015-12-03 17:17:45 UTC 
Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/

If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release.
Note You need to log in before you can comment on or make changes to this bug.