Bug 1695081

Summary:	Log level changes do not take effect until the process is restarted
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Nithya Balachandran <nbalacha>
Component:	glusterfs	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED ERRATA	QA Contact:	Kshithij Iyer <kiyer>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.4	CC:	amukherj, kiyer, moagrawa, rhinduja, rhs-bugs, sheggodu, vbellur
Target Milestone:	---
Target Release:	RHGS 3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0-2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1696046 1699715 (view as bug list)		Environment:
Last Closed:	2019-10-30 12:20:50 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:
Bug Blocks:	1696046, 1696807, 1699715

Description Nithya Balachandran 2019-04-02 12:55:21 UTC

Description of problem:

Changing the log level of a running client does not take effect until the process is restarted.


Version-Release number of selected component (if applicable):
RHGS 3.4.2 onwards

How reproducible:
Always


Steps to Reproduce:
1.Create a volume and fuse mount it
2.Tail the mnt log and keep watching the messages logged
3.Set client-log-level to TRACE
4.Create some files on the mount point


Actual results:
No trace messages are logged

Expected results:
Trace messages should be logged



Additional info:
Trace messages start being logged when the volume is unmounted and remounted.


Impact : This affects our ability to debug live systems.


This was introduced by 
commit 56fb13d05cb4465c14cc231bab1296a48c33c57d. "glusterfs: During reconfigure set log-level per xlator level"

Comment 13 errata-xmlrpc 2019-10-30 12:20:50 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:3249