Bug 763701 (GLUSTER-1969)

Summary:	Inaccurate log message on 'volume set'
Product:	[Community] GlusterFS	Reporter:	Vikas Gorur <vikas>
Component:	cli	Assignee:	Kaushal <kaushal>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	3.1.0	CC:	gluster-bugs, vijay
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:	2012-04-27 05:10:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vikas Gorur 2010-10-18 20:00:22 UTC

[root@brick5 qa]# gluster volume set qa diagnostics.client-log-level TRACE
Set volume successful

[root@brick5 qa]# gluster volume set qa spam.client-log-level TRACE
Set volume unsuccessful
option : spam.client-log-level does not exist

"set volume successful" is an inaccurate message. What is being set is an option on a volume. A more appropriate message would be:

Set 'diagnostics.client-log-level=TRACE' on volume 'qa' successful

Similarly for the unsuccessful case.

Comment 1 Amar Tumballi 2011-04-25 09:33:48 UTC

Please update the status of this bug as its been more than 6months since its filed (bug id < 2000)

Please resolve it with proper resolution if its not valid anymore. If its still valid and not critical, move it to 'enhancement' severity.

Comment 2 kaushik 2011-05-02 03:29:13 UTC

(In reply to comment #1)
Had sent a patch will rebase it and send it again.

Comment 3 Kaushal 2012-04-27 05:09:54 UTC

Closing as wontfix. File a new bug if this is required.