Bug 764560 (GLUSTER-2828)

Summary: gluster geo-rep stop should not show unsuccessful when the status is corrupt
Product: [Community] GlusterFS Reporter: kaushik <kbudiger>
Component: geo-replicationAssignee: Venky Shankar <vshankar>
Status: CLOSED CURRENTRELEASE QA Contact: Vijaykumar Koppad <vkoppad>
Severity: medium Docs Contact:
Priority: medium    
Version: mainlineCC: bbandari, csaba, gluster-bugs, lakshmipathi, vbellur
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.4.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-24 17:44:15 UTC Type: ---
Regression: RTNR Mount Type: ---
Documentation: --- CRM:
Verified Versions: 3.3.0qa45 Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 817967    

Description kaushik 2011-04-21 16:33:59 UTC
When the monitor is killed , and if we stop the geo-rep from command line,
we get a msg:
warning: geo-replication session isnot running
geo-replication command failed

We should not should show failed command should just show the warning & and say returned succesfully

Comment 1 Csaba Henk 2011-04-28 06:37:20 UTC
The not-fail part was working properly earlier, regression brought in by commit c034f263. The show-warning part is TBD as of the creation of this bz entry.

Comment 2 Anand Avati 2011-05-09 17:26:55 UTC
PATCH: http://patches.gluster.com/patch/7092 in master (syncdaemon: add --normalize-url option)

Comment 3 Anand Avati 2011-05-30 05:49:36 UTC
PATCH: http://patches.gluster.com/patch/7184 in master (mgmt/glusterd: Display a warning message to CLI in case of a corrupt geo-rep session)

Comment 4 Lakshmipathi G 2011-09-14 04:07:47 UTC
testing with 3.2.3 - It says "geo-replication command failed"

killed monitor & trying to stop -

#  gluster volume geo-replication gsync root.1.108:/slave44 status
MASTER               SLAVE                                              STATUS    
--------------------------------------------------------------------------------
gsync                root.1.108:/slave44                        corrupt   

#  gluster volume geo-replication gsync root.1.108:/slave44 stop  
warning: geo-replication session isnot running
geo-replication command failed

Comment 5 kaushik 2011-09-14 08:30:39 UTC
PATCH: http://patches.gluster.com/patch/7184 should be back-ported to release-3.2 branch.

Comment 6 Csaba Henk 2011-10-02 03:12:19 UTC
Kaushik, then please do the backport (when that's being committed, let's close the bug).

Comment 7 Vijaykumar Koppad 2012-05-31 12:08:32 UTC
Although this bug was in release-3.2. I still tested it on 3.3.0qa45. It behaves properly.