REVIEW: http://review.gluster.org/13640 (glusterd: DEBUG log should not come after resetting client log level) posted (#1) for review on release-3.7 by Gaurav Kumar Garg (ggarg)

REVIEW: http://review.gluster.org/13640 (glusterd: DEBUG log should not come after resetting client log level) posted (#2) for review on release-3.7 by Gaurav Kumar Garg (ggarg)

REVIEW: http://review.gluster.org/13640 (glusterd: DEBUG log should not come after resetting client log level) posted (#3) for review on release-3.7 by Gaurav Kumar Garg (ggarg)

REVIEW: http://review.gluster.org/13640 (glusterd: DEBUG log should not come after resetting client log level) posted (#4) for review on release-3.7 by Gaurav Kumar Garg (ggarg)

COMMIT: http://review.gluster.org/13640 committed in release-3.7 by Atin Mukherjee (amukherj) 
------
commit c713c94d9173e72ee6a60e64f001bdb6a35d8cf0
Author: Gaurav Kumar Garg <garg.gaurav52>
Date:   Wed Aug 12 01:09:41 2015 +0530

    glusterd: DEBUG log should not come after resetting client log level
    
    This patch is backport of: http://review.gluster.org/#/c/11887/
    
    After resetting diagnostics.client-log-level option still DEBUG log is
    logging in scrubber and bitrot log file. After resetting any option
    value of that options goes to default value.
    
    This patch will set the default value of client and brick log level to
    "INFO" log level.
    
    Change-Id: I4cf04754dcf5ddc908dae4d9bdf525cfcd6cc2bd
    BUG: 1315628
    Signed-off-by: Gaurav Kumar Garg <ggarg>
    
      >> Change-Id: I4cf04754dcf5ddc908dae4d9bdf525cfcd6cc2bd
      >> BUG: 1252696
      >> Signed-off-by: Gaurav Kumar Garg <ggarg>
      >> Reviewed-on: http://review.gluster.org/11887
      >> Tested-by: NetBSD Build System <jenkins.org>
      >> Tested-by: Gluster Build System <jenkins.com>
      >> Reviewed-by: Atin Mukherjee <amukherj>
    (cherry picked from commit 6e17fb2097f941798e1d56728fd3d61e525a39a5)
    
    Change-Id: I1e08402d6b613c7afee611c81c9efb456ec6f4f0
    Reviewed-on: http://review.gluster.org/13640
    Tested-by: Gaurav Kumar Garg <ggarg>
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Atin Mukherjee <amukherj>

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.10, please open a new bug report.

glusterfs-3.7.10 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://www.gluster.org/pipermail/gluster-users/2016-April/026164.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user