[Bugs] [Bug 1499159] [geo-rep]: Improve the output message to reflect the real failure with schedule_georep script

bugzilla at redhat.com bugzilla at redhat.com
Fri Oct 6 09:39:42 UTC 2017


Kotresh HR <khiremat at redhat.com> changed:

           What    |Removed                     |Added
             Status|NEW                         |ASSIGNED
            Version|3.12                        |mainline
           Assignee|bugs at gluster.org            |khiremat at redhat.com

--- Comment #1 from Kotresh HR <khiremat at redhat.com> ---

Description of problem:

Currently if we manually check the geo-rep status or stop it with "invalid
slave host, or slave volume". It throws right warning as:

[root at dhcp42-79 MASTER]# gluster volume geo-replication MASTER status 
No active geo-replication sessions between MASTER and
[root at dhcp42-79 MASTER]# gluster volume geo-replication MASTER stop
Geo-replication session between MASTER and does not exist.
geo-replication command failed
[root at dhcp42-79 MASTER]#

But if schedule_georep script is passed with invalid slave host and volume
information it fails with "commit failed on localhost" as:

[root at dhcp42-79 MASTER]# time python
/usr/share/glusterfs/scripts/schedule_georep.py MASTER SLAVE
Commit failed on localhost. Please check the log file for more details.

The problem with above output is it doesnt give picture whether something is
down at slave (gsyncd, slave volume) or wrong slave information is provided.
Also, which logs should user look into?

If geo-replication stop/status has failed, it should print the similar messages
as it prints when executed manually. 

Version-Release number of selected component (if applicable):


You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list