[Bugs] [Bug 1693401] New: client-log-level and brick-log-level options are not properly handled in latest codebase

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1693401

            Bug ID: 1693401
           Summary: client-log-level and brick-log-level options are not
                    properly handled in latest codebase
           Product: GlusterFS
           Version: mainline
            Status: NEW
         Component: core
          Severity: high
          Priority: high
          Assignee: bugs at gluster.org
          Reporter: atumball at redhat.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community



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

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.