Bug 1699271

Summary: [geo-rep]: Geo-rep FAULTY in RHGS 3.5
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Rochelle <rallan>
Component: geo-replicationAssignee: Sunny Kumar <sunkumar>
Status: CLOSED ERRATA QA Contact: Rahul Hinduja <rhinduja>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rhgs-3.5CC: amukherj, avishwan, csaba, khiremat, pasik, rhinduja, rhs-bugs, sheggodu, storage-qa-internal, sunkumar
Target Milestone: ---Keywords: Regression
Target Release: RHGS 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-6.0-2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1699394 (view as bug list) Environment:
Last Closed: 2019-10-30 12:20:51 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1696807, 1699394, 1770100    

Description Rochelle 2019-04-12 09:42:55 UTC 
Description of problem:
=======================
Geo-replication is faulty on RHGS 3.5


The logs throw the following warning: 
[2019-04-11 03:03:06.736471] W [gsyncd(config-get):305:main] <top>: Session config file not exists, using the default config    path=/var/lib/glusterd/geo-replication/master_10.70.42.250_slave/gsyncd.conf

Is this a new prerequisite for setting up geo-rep in RHGS 3.5 ?


Also, the following OSErrors can be seen in the master:
-------------------------------------------------------
[2019-04-11 03:03:56.53394] E [repce(agent /rhs/brick2/b4):122:worker] <top>: call failed:
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):
=============================================================
glusterfs-6.0-1.el7rhgs.x86_64
gluster-nagios-common-0.2.4-1.el7rhgs.noarch
glusterfs-fuse-6.0-1.el7rhgs.x86_64
glusterfs-api-6.0-1.el7rhgs.x86_64
python2-gluster-6.0-1.el7rhgs.x86_64
glusterfs-geo-replication-6.0-1.el7rhgs.x86_64
gluster-nagios-addons-0.2.10-2.el7rhgs.x86_64
glusterfs-libs-6.0-1.el7rhgs.x86_64
glusterfs-client-xlators-6.0-1.el7rhgs.x86_64
glusterfs-rdma-6.0-1.el7rhgs.x86_64
libvirt-daemon-driver-storage-gluster-4.5.0-10.el7_6.6.x86_64
glusterfs-server-6.0-1.el7rhgs.x86_64
vdsm-gluster-4.19.43-2.3.el7rhgs.noarch
glusterfs-cli-6.0-1.el7rhgs.x86_64


How reproducible:
================
Always

Steps to Reproduce:
==================
The same steps to set up geo-replication as mentioned in RHGS documentation

Actual results:
===============
Geo-rep status is FAULTY

Expected results:
=================
Geo-rep status should be ACTIVE/PASSIVE


Additional info:
===============
Will be attaching sosreports
Comment 13 errata-xmlrpc 2019-10-30 12:20:51 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.

https://access.redhat.com/errata/RHEA-2019:3249