Bug 1693401

Summary:	client-log-level and brick-log-level options are not properly handled in latest codebase
Product:	[Community] GlusterFS	Reporter:	Amar Tumballi <atumball>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-25 13:25:20 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 Amar Tumballi 2019-03-27 18:28:44 UTC

Description of problem:
If we set client-log-level option to TRACE, the behavior was not as expected.

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

How reproducible:
100%

Steps to Reproduce:
1. glusterd;  create volume; start volume; mount volume;
2. gluster volume set volume client-log-level TRACE
3. Notice that the client log file is not dumping all the TRACE level logs.

4. gluster volume set volume brick-log-level TRACE
5. Notice that the brick log file is not dumping all the TRACE level logs.



Actual results:
No proper logging, causing issues with debugging.

Expected results:
Log files should start showing corresponding level logs immediately.


Additional info:
Looks like this got introduced by https://review.gluster.org/21470

Comment 1 Worker Ant 2019-03-27 18:32:13 UTC

REVIEW: https://review.gluster.org/22426 (xlators: make the 'handle_default_options()' as dummy function.) posted (#2) for review on master by Amar Tumballi

Comment 2 Amar Tumballi 2019-06-25 13:25:20 UTC

Mohit fixed the issue with another patch, and the hypothesis in this bug was wrong.