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
REVIEW: https://review.gluster.org/22426 (xlators: make the 'handle_default_options()' as dummy function.) posted (#2) for review on master by Amar Tumballi
Mohit fixed the issue with another patch, and the hypothesis in this bug was wrong.