Bug 1308904 - volume reset of log levels does not return them to the default
Summary: volume reset of log levels does not return them to the default
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.7.7
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On: 1308902
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-16 12:21 UTC by Niels de Vos
Modified: 2017-01-23 05:15 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-01-23 05:15:14 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Niels de Vos 2016-02-16 12:21:05 UTC 
+++ 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.
Comment 1 Atin Mukherjee 2016-06-23 17:22:39 UTC 
This is fixed in latest releases (3.7 & 3.8) of GlusterFS with http://review.gluster.org/#/c/11887
Note You need to log in before you can comment on or make changes to this bug.