Bug 764930 (GLUSTER-3198) - log level cannot be set back to INFO level
Summary: log level cannot be set back to INFO level
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-3198
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Raghavendra Bhat
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-20 06:15 UTC by Raghavendra Bhat
Modified: 2011-07-25 05:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

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

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.
Note You need to log in before you can comment on or make changes to this bug.