Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1503424

Summary:	server.allow-insecure should be visible in "gluster volume set help"
Product:	[Community] GlusterFS	Reporter:	Sanju <srakonde>
Component:	glusterd	Assignee:	Sanju <srakonde>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	amukherj, anekkunt, bugs, lmohanty, nlevinki, rhs-bugs, rwheeler, sasundar, smohan, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.13.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1284390
Clones:	1505373 (view as bug list)		Environment:
Last Closed:	2017-12-08 17:44:30 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:	996511, 1284390, 1503423
Bug Blocks:	1505373

Description Sanju 2017-10-18 06:07:47 UTC

+++ This bug was initially created as a clone of Bug #1284390 +++

Comment 1 Worker Ant 2017-10-18 06:15:29 UTC

REVIEW: https://review.gluster.org/18544 (glusterd: documenting server.allow-insecure) posted (#1) for review on master by Sanju Rakonde (srakonde)

Comment 2 Worker Ant 2017-10-18 14:23:50 UTC

COMMIT: https://review.gluster.org/18544 committed in master by Jeff Darcy (jeff.us) 
------
commit c0b08f10ed07bfe06309e31a7fff85cadb733ce2
Author: Sanju Rakonde <srakonde>
Date:   Wed Oct 18 11:40:59 2017 +0530

    glusterd: documenting server.allow-insecure
    
    problem: "server.allow-insecure" is invisible in gluster volume set
    help.
    
    Fix: "server.allow-insecure" is defined as NO_DOC type, chainging
    it to DOC type solve the problem.
    
    Change-Id: I327f1e4c1684ff846deb8b7df07d4d8a09073274
    BUG: 1503424
    Signed-off-by: Sanju Rakonde <srakonde>

Comment 3 Shyamsundar 2017-12-08 17:44:30 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.13.0, please open a new bug report.

glusterfs-3.13.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-December/000087.html
[2] https://www.gluster.org/pipermail/gluster-users/