Bug 1597511

Summary:	introduce cluster.daemon-log-level option
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Atin Mukherjee <amukherj>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED ERRATA	QA Contact:	Bala Konda Reddy M <bmekala>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.4	CC:	bmekala, rcyriac, rhs-bugs, sankarshan, storage-qa-internal, vbellur
Target Milestone:	---
Target Release:	RHGS 3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.12.2-14	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1597509	Environment:
Last Closed:	2018-09-04 06:49: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:	1597473, 1597509
Bug Blocks:	1466455, 1503137, 1597663

Comment 4 Bala Konda Reddy M 2018-07-23 11:27:30 UTC

BUILD: 3.12.2-14

1. Created a replicated volume (1X3)
2. Enabled quota and uss, mounted the volume an performed untar of Linux kernel
3. Changed the cluster.daemon-log-level from INFO to DEBUG and restarted the volume, In shd and quota logs seen 'D' messages
4. Changed from DEBUG to TRACE and restarted the volume, seen 'T' messages in the respective logs in all the nodes
5. Changed from Trace to WARNING and restarted the volume, seen 'W' messages in the respective logs in all the nodes
6. Changed from WARNING to INFO and restarted the volume, seen 'I' messages in the respective logs in all the nodes
7. Changed from INFO to TRACE and restarted the volume, seen 'T' messages in the respective logs in all the nodes.

cluster.daemon-log-level option is working properly

Hence marking it as verified

Comment 5 errata-xmlrpc 2018-09-04 06:49:14 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/RHSA-2018:2607