Bug 764521 (GLUSTER-2789) - handling of invalid config options is broken again
Summary: handling of invalid config options is broken again
Keywords:
Status: CLOSED DUPLICATE of bug 764468
Alias: GLUSTER-2789
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Csaba Henk
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-17 18:17 UTC by Csaba Henk
Modified: 2011-04-18 12:20 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 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 ***
Note You need to log in before you can comment on or make changes to this bug.