[Bugs] [Bug 1308904] New: volume reset of log levels does not return them to the default

[bugzilla at redhat.com]

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

            Bug ID: 1308904
           Summary: volume reset of log levels does not return them to the
                    default
           Product: GlusterFS
           Version: 3.7.7
         Component: glusterd
          Keywords: Triaged
          Severity: low
          Assignee: bugs at gluster.org
          Reporter: ndevos at redhat.com
                CC: amukherj at redhat.com, bugs at gluster.org,
                    ggarg at redhat.com, hgowtham at redhat.com,
                    joe at julianfamily.org, kaushal at redhat.com
        Depends On: 1308902



+++ This bug was initially created as a clone of Bug #1308902 +++
+++                                                           +++
+++ Use this bug to provide a fix in the release-3.7 branch.  +++

If you change the log level

    gluster volume set myvol diagnostics.brick-log-level DEBUG

then reset the log level

    gluster volume reset myvol diagnostics.brick-log-level

the process will continue to log at the DEBUG level instead of returning to
INFO despite resetting the value in glusterd's view of the graph - removing it
from gluster volume info.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1308902
[Bug 1308902] volume reset of log levels does not return them to the
default
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.