Bug 764521 (GLUSTER-2789)

Summary: handling of invalid config options is broken again
Product: [Community] GlusterFS Reporter: Csaba Henk <csaba>
Component: geo-replicationAssignee: Csaba Henk <csaba>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: mainlineCC: 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 Csaba Henk 2011-04-17 18:17:54 UTC
getting invalid option blows up:

# gluster volume geo-replication config pop /scratch/fex0 foo
[2011-04-17 20:11:58.15312] E [syncdutils:131:log_raise_exception] <top>: FAIL:
Traceback (most recent call last):
  File "/meta/progs/glusterfs-git/usr/libexec/glusterfs/python/syncdaemon/gsyncd.py", line 102, in main
    main_i()
  File "/meta/progs/glusterfs-git/usr/libexec/glusterfs/python/syncdaemon/gsyncd.py", line 219, in main_i
    raise RuntimeError("not a valid option: " + confdata.opt)
RuntimeError: not a valid option: foo
failed with RuntimeError.

setting invalid option seemingly succeeds:

# gluster volume geo-replication config pop /scratch/fex0 foo bar
geo-replication config updated successfully

... although it doesn't get through:

# gluster volume geo-replication config pop /scratch/fex0 | grep foo | wc -l
0

Comment 1 Csaba Henk 2011-04-18 09:20:04 UTC
Caused by a mistake in one of the gsyncd termination cleanup patches, therefore it belongs to that problem circle.

*** This bug has been marked as a duplicate of bug 2736 ***