Bug 1308904

Summary:	volume reset of log levels does not return them to the default
Product:	[Community] GlusterFS	Reporter:	Niels de Vos <ndevos>
Component:	glusterd	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.7.7	CC:	amukherj, bugs, hgowtham, joe, kaushal, smohan
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-23 05:15:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1308902
Bug Blocks:

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