Bug 764930 (GLUSTER-3198)

Summary:	log level cannot be set back to INFO level
Product:	[Community] GlusterFS	Reporter:	Raghavendra Bhat <rabhat>
Component:	glusterd	Assignee:	Raghavendra Bhat <rabhat>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Raghavendra Bhat 2011-07-20 06:15:09 UTC

gluster command for the changing the log-level for client or server fails if the log-level is given as INFO.


gluster volume set mirror client-log-level INFO
option log-level INFO: 'INFO' is not valid (possible options are DEBUG, WARNING, ERROR, CRITICAL, NONE, TRACE, )

Comment 1 Anand Avati 2011-07-20 10:15:45 UTC

CHANGE: http://review.gluster.com/43 (Change-Id: Ieba6591b0641dcb7dad724c1d8199dc5e91b6bfd) merged in master by Anand Avati (avati)

Comment 2 Anand Avati 2011-07-20 10:17:12 UTC

CHANGE: http://review.gluster.com/57 (Change-Id: Ica9ea1b129e2c8325f7eafae7a83b85734153663) merged in release-3.2 by Anand Avati (avati)

Comment 3 Raghavendra Bhat 2011-07-25 02:34:25 UTC

Its fixed now. Log-level of the bricks or the clients can be changed to INFO level now.