[Bugs] [Bug 1315628] After resetting diagnostics.client-log-level, still Debug messages are logging in scrubber log

[bugzilla at redhat.com]

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



--- Comment #5 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13640 committed in release-3.7 by Atin
Mukherjee (amukherj at redhat.com) 
------
commit c713c94d9173e72ee6a60e64f001bdb6a35d8cf0
Author: Gaurav Kumar Garg <garg.gaurav52 at gmail.com>
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 at redhat.com>

      >> Change-Id: I4cf04754dcf5ddc908dae4d9bdf525cfcd6cc2bd
      >> BUG: 1252696
      >> Signed-off-by: Gaurav Kumar Garg <ggarg at redhat.com>
      >> Reviewed-on: http://review.gluster.org/11887
      >> Tested-by: NetBSD Build System <jenkins at build.gluster.org>
      >> Tested-by: Gluster Build System <jenkins at build.gluster.com>
      >> Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    (cherry picked from commit 6e17fb2097f941798e1d56728fd3d61e525a39a5)

    Change-Id: I1e08402d6b613c7afee611c81c9efb456ec6f4f0
    Reviewed-on: http://review.gluster.org/13640
    Tested-by: Gaurav Kumar Garg <ggarg at redhat.com>
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>

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