Bug 1000922

Summary: Dist-geo-rep : geo-rep config log-level option takes invalid values and makes geo-rep status defunct
Product: Red Hat Gluster Storage Reporter: Vijaykumar Koppad <vkoppad>
Component: geo-replicationAssignee: Ajeet Jha <ajha>
Status: CLOSED ERRATA QA Contact: Vijaykumar Koppad <vkoppad>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1CC: aavati, amarts, asriram, bbandari, csaba, grajaiya, nsathyan, rhs-bugs, shaines, vagarwal, vshankar
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.4.0.34rhs Doc Type: Bug Fix
Doc Text:
Previously, the input for "log-level" configuration option of geop-replication was not validated. Now, an error message is displayed when user attempts to give invalid options.
 Story Points: ---
Clone Of:
: 1010874 (view as bug list) Environment:
Last Closed: 2013-11-27 15:32:52 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:

Description Vijaykumar Koppad 2013-08-26 06:42:20 UTC 
Description of problem: The geo-rep config log-level option takes invalid values  and makes geo-rep status defunct. 

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[root@redlemon ~]# gluster v geo  master root.43.25::slave config log-level Afafaef
geo-replication config updated successfully
[root@redlemon ~]# gluster v geo  master root.43.25::slave status
NODE                       MASTER    SLAVE                      HEALTH     UPTIME       
------------------------------------------------------------------------------------
redlemon.blr.redhat.com    master    root.43.25::slave    defunct    N/A          
redmoon.blr.redhat.com     master    root.43.25::slave    defunct    N/A          
redwood.blr.redhat.com     master    root.43.25::slave    defunct    N/A          
redcloud.blr.redhat.com    master    root.43.25::slave    defunct    N/A  
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Problem with this is , it can't be recovered just by resetting it, you have to stop and start the session. 

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[root@redlemon ~]# gluster v geo  master root.43.25::slave config \!log-level 
geo-replication config updated successfully
[root@redlemon ~]# gluster v geo  master root.43.25::slave status
NODE                       MASTER    SLAVE                      HEALTH     UPTIME       
------------------------------------------------------------------------------------
redlemon.blr.redhat.com    master    root.43.25::slave    defunct    N/A          
redwood.blr.redhat.com     master    root.43.25::slave    defunct    N/A          
redmoon.blr.redhat.com     master    root.43.25::slave    defunct    N/A          
redcloud.blr.redhat.com    master    root.43.25::slave    defunct    N/A

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>



Version-Release number of selected component (if applicable):glusterfs-3.4.0.22rhs-2.el6rhs.x86_64


How reproducible:happens everytime


Steps to Reproduce:
1.create and start a geo-rep relationship between master and slave. 
2.set config log-level to some random value
3.check the geo-rep status


Actual results: The geo-rep status becomes defunct 


Expected results:It should error out properly if it get wrong values.


Additional info:
Comment 2 Amar Tumballi 2013-09-24 07:32:04 UTC 
upstream fix @ http://review.gluster.org/5989
Comment 3 Amar Tumballi 2013-10-07 06:39:58 UTC 
https://code.engineering.redhat.com/gerrit/#/c/13677
Comment 4 Gowrishankar Rajaiyan 2013-10-08 08:41:31 UTC 
Fixed in version please.
Comment 5 Vijaykumar Koppad 2013-10-15 09:56:36 UTC 
verified on glusterfs-3.4.0.34rhs
Comment 7 errata-xmlrpc 2013-11-27 15:32:52 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1769.html