Bug 1652852

Summary:	"gluster volume get" doesn't show real default value for server.tcp-user-timeout
Product:	[Community] GlusterFS	Reporter:	Xavi Hernandez <jahernan>
Component:	glusterd	Assignee:	Xavi Hernandez <jahernan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-25 16:32:14 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:

Description Xavi Hernandez 2018-11-23 10:03:54 UTC

Description of problem:

When "gluster volume get" is executed on a volume with default options, the value of "server.tcp-user-timeout" is reported as "0", but its real default value is "42".

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


How reproducible:

Always

Steps to Reproduce:
1. gluster volume create test host:/brick
2. gluster volume get test server.tcp-user-timeout
3.

Actual results:

The value shown is "0"

Expected results:

It should show "42"


Additional info:

This happens because glusterd doesn't look for default values for options at the same places that xlators are actually using when running.

Comment 1 Worker Ant 2018-11-23 10:07:13 UTC

REVIEW: https://review.gluster.org/21709 (core: create a constant for default network timeout) posted (#1) for review on master by Xavi Hernandez

Comment 2 Worker Ant 2018-11-24 17:20:54 UTC

REVIEW: https://review.gluster.org/21709 (core: create a constant for default network timeout) posted (#1) for review on master by Xavi Hernandez

Comment 3 Shyamsundar 2019-03-25 16:32:14 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-6.0, please open a new bug report.

glusterfs-6.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] https://lists.gluster.org/pipermail/announce/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/