Bug 1693401 - client-log-level and brick-log-level options are not properly handled in latest codebase
Summary: client-log-level and brick-log-level options are not properly handled in late...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-27 18:28 UTC by Amar Tumballi
Modified: 2019-06-25 13:25 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-06-25 13:25:20 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22426 0 None Abandoned xlators: make the 'handle_default_options()' as dummy function. 2019-04-15 02:51:06 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.