Red Hat Bugzilla – Bug 989248
Dist-geo-rep : 'gluster volume geo <master_vol> <slave_ip>::<slave_vol> stop' gives wrong error message if session does not exist
Last modified: 2015-04-20 07:58:03 EDT
Description of problem:
Dist-geo-rep : 'gluster volume geo <master_vol> <slave_ip>::<slave_vol> stop' gives wrong error message if session does not exist.
(slave host is reachable)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
[root@DVM1 ~]# gluster volume geo test5 rhsauto027.lab.eng.blr.redhat.com::slave2 stop
geo-replication session b/w test5 & rhsauto027.lab.eng.blr.redhat.com::slave2 is not running on this node.
geo-replication command failed
If session does not exist, it should not say session is not running on this node.
Should say session does not exist
Performing statefile check in case of geo-rep stop, so as to provide proper error message in case session is not created.
However in case of geo-rep stop force, we allow the command to succeed even in case that the session is not created, because the stop command is a failsafe command to stop running geo-rep sessions on any nodes.
verified with -220.127.116.11rhs-1.el6rhs.x86_64
working as per expected result , hence moving to verified
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.