Description of problem: When you reset a log level, the log continues to log at the last set log level despite resetting it with regard to "volume info". Version-Release number of selected component (if applicable): 3.4.2 How reproducible: always Steps to Reproduce: 1. gluster volume set diagnostics.client-log-level DEBUG 2. gluster volume reset diagnostics.client-log-level Actual results: The client log will continue to log at DEBUG Expected results: The client log should be reset to INFO Additional info: The same is true for brick-log-level
GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5. This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "bugs". If there is no response by the end of the month, this bug will get automatically closed.
GlusterFS 3.4.x has reached end-of-life. If this bug still exists in a later release please reopen this and change the version or open a new bug.