Description of problem:
Some users are facing problem in configuring this option on gluster-users. So it is better to make this easier by providing the command on gluster volume set.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
REVIEW: http://review.gluster.org/9516 (mgmt/glusterd: Add bind-insecure option) posted (#1) for review on master by Pranith Kumar Karampuri (firstname.lastname@example.org)
REVIEW: http://review.gluster.org/9516 (mgmt/glusterd: Add bind-insecure option) posted (#2) for review on master by Pranith Kumar Karampuri (email@example.com)
COMMIT: http://review.gluster.org/9516 committed in master by Kaushal M (firstname.lastname@example.org)
Author: Pranith Kumar K <email@example.com>
Date: Sat Jan 31 00:32:05 2015 +0530
mgmt/glusterd: Add bind-insecure option
Also deleted default values for disperse-self-heal-daemon and locks.trace
Signed-off-by: Pranith Kumar K <firstname.lastname@example.org>
Reviewed-by: Atin Mukherjee <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Kaushal M <email@example.com>
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.7.0, please open a new bug report.
glusterfs-3.7.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.