Bug 1306877 - volume reset of log levels does not return them to the default [NEEDINFO]
Summary: volume reset of log levels does not return them to the default
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.6.8
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-12 00:18 UTC by Joe Julian
Modified: 2019-11-11 14:09 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-01 04:42:38 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
amukherj: needinfo?

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Joe Julian 2016-02-12 00:18:41 UTC 
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-22 07:19:04 UTC 
This is fixed in latest releases (3.7 & 3.8) of GlusterFS with http://review.gluster.org/#/c/11887 , given that 3.6 will be EOLed once 3.9 is out (in another 3 months) do you see a strong reason to backport it to 3.6 branch?
Comment 2 Atin Mukherjee 2016-08-01 04:42:38 UTC 
This is not a security bug, not going to fix this in 3.6.x because of
http://www.gluster.org/pipermail/gluster-users/2016-July/027682.html
Comment 3 Atin Mukherjee 2016-08-01 04:43:58 UTC 
If the issue persists in the latest releases, please feel free to clone them
Note You need to log in before you can comment on or make changes to this bug.