Bug 847846

Summary: gluster volume reset of single option does not work.
Product: [Community] GlusterFS Reporter: Pranith Kumar K <pkarampu>
Component: glusterdAssignee: Krutika Dhananjay <kdhananj>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: csaba, gluster-bugs
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:
: 852143 (view as bug list) Environment:
Last Closed: 2013-07-24 13:48:23 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Bug Depends On:    
Bug Blocks: 852143    

Description Pranith Kumar K 2012-08-13 14:12:41 EDT
Description of problem:
Problem exists even in 3.3.0
[root@pranithk-laptop ~]# gluster volume info
 
Volume Name: vol
Type: Distribute
Volume ID: 6f3224f5-f827-4764-9673-1c73fb75492e
Status: Created
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: 192.168.122.1:/tmp/0
Options Reconfigured:
diagnostics.client-log-level: DEBUG
[root@pranithk-laptop ~]# gluster volume reset vol client-log-level 
reset volume successful
[root@pranithk-laptop ~]# gluster volume info
 
Volume Name: vol
Type: Distribute
Volume ID: 6f3224f5-f827-4764-9673-1c73fb75492e
Status: Created
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: 192.168.122.1:/tmp/0
Options Reconfigured:
diagnostics.client-log-level: DEBUG
[root@pranithk-laptop ~]# gluster volume reset vol 
reset volume successful
[root@pranithk-laptop ~]# gluster volume info
 
Volume Name: vol
Type: Distribute
Volume ID: 6f3224f5-f827-4764-9673-1c73fb75492e
Status: Created
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: 192.168.122.1:/tmp/0
[root@pranithk-laptop ~]# 

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


How reproducible:


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


Expected results:


Additional info:
Comment 1 Csaba Henk 2012-08-31 13:01:45 EDT
@pranith:

As of the message of the proposed fix -- http://review.gluster.org/3860 -- and also my experience,

  gluster volume reset vol client-log-level

(as you have in the report) works as expected; the problematic case is when a
fully qualified option name is used (like diagnostics.client-log-level).

Please confirm/clarify whether it is the issue.
Comment 2 Pranith Kumar K 2012-08-31 13:33:33 EDT
Yes. Wrong copy paste I guess :-(. Logged this bug pretty late in the night. I did explain it correctly to krutika.