+++ This bug was initially created as a clone of Bug #1699271 +++
Description of problem:
=======================
Geo-replication goes faulty
Traceback (most recent call last):
File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 118, in worker
res = getattr(self.obj, rmeth)(*in_data[2:])
File "/usr/libexec/glusterfs/python/syncdaemon/changelogagent.py", line 37, in init
return Changes.cl_init()
File "/usr/libexec/glusterfs/python/syncdaemon/changelogagent.py", line 21, in __getattr__
from libgfchangelog import Changes as LChanges
File "/usr/libexec/glusterfs/python/syncdaemon/libgfchangelog.py", line 18, in <module>
class Changes(object):
File "/usr/libexec/glusterfs/python/syncdaemon/libgfchangelog.py", line 20, in Changes
use_errno=True)
File "/usr/lib64/python2.7/ctypes/__init__.py", line 360, in __init__
self._handle = _dlopen(self._name, mode)
OSError: libgfchangelog.so: cannot open shared object file: No such file or directory
Version-Release number of selected component (if applicable):
=============================================================
mainline
How reproducible:
================
Always
Actual results:
===============
Geo-rep status is FAULTY
Expected results:
=================
Geo-rep status should be ACTIVE/PASSIVE