Bug 823403

Summary:	log-level inputs are case sensitive
Product:	[Community] GlusterFS	Reporter:	Anush Shetty <ashetty>
Component:	logging	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	mainline	CC:	gluster-bugs, grajaiya, ujjwala, vraman
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.4.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-24 17:15:39 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:

Description Anush Shetty 2012-05-21 07:30:19 UTC

Description of problem: Currently, the log level input is case sensitive. It would be good to make it case insensitive




Version-Release number of selected component (if applicable): Upstream


How reproducible: N/A


Steps to Reproduce:
1.
2.
3.
  
Actual results:

mount -t glusterfs -o log-level=debug ec2-50-112-27-254.us-west-2.compute.amazonaws.com:/distrep1 /mnt
invalid log level debug, using INFO

Comment 1 Gowrishankar Rajaiyan 2012-05-28 07:24:39 UTC

[root@dhcp201-154 ~]# mount -t glusterfs -o log-level=debug dhcp201-181.englab.pnq.redhat.com:test1 /tmp/test1
invalid log level debug, using INFO
[root@dhcp201-154 ~]# 


Tested in version: glusterfs-server-3.3.0qa43-1.el6.x86_64

Comment 2 Amar Tumballi 2012-05-30 06:08:46 UTC

Not going to fix it in release-3.3 branch, unless there is a absolute need. Hence this is present only in master branch. Will be able to test with a 'git pull' of master branch.

Comment 3 Amar Tumballi 2012-06-01 06:53:55 UTC

the bug fix is only in upstream, not in release-3.3. Hence moving it out of the ON_QA, and setting MODIFIED (as a standard practice @ Red Hat)