Bug 1165142

Summary:	hardcoded gsyncd path causes geo-replication to fail on non-redhat systems
Product:	[Community] GlusterFS	Reporter:	Kaleb KEITHLEY <kkeithle>
Component:	geo-replication	Assignee:	bugs <bugs>
Status:	CLOSED EOL	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.5.3	CC:	avishwan, bugs, cww, jordan.tomkinson, kkeithle
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1162905	Environment:
Last Closed:	2016-06-17 15:56:43 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:	1162905, 1304692
Bug Blocks:	1165140

Description Kaleb KEITHLEY 2014-11-18 12:27:43 UTC

+++ This bug was initially created as a clone of Bug #1162905 +++

Description of problem:
Line 16 of geo-replication/src/peer_gsec_create.in has a hard coded path of ${exec_prefix}/libexec/glusterfs/gsyncd - ignoring the value of remote_gsyncd option in gsyncd.conf

atleast in Ubuntu, there is no libexec folder anywhere on the system and the ubuntu debs provided by semiosis installs gsyncd to /usr/lib/x86_64-linux-gnu/glusterfs/

this file has not changed in 3.5 or 3.6, so affects both releases.

The only way to get distributed geo-replication working is to symlink the path to the correct location.

Version-Release number of selected component (if applicable): 3.5.1, 3.5.2, 3.6.1


How to reproduce:

follow the distributed geo-replication docs at https://github.com/gluster/glusterfs/blob/master/doc/admin-guide/en-US/markdown/admin_distributed_geo_rep.md on a non-redhat system


Steps to Reproduce:
1. setup geo-replication as per docs
2. start the geo-replication
3. status never changes from "Not Active"
4. log files show cannot execute gsyncd

Actual results:

E [glusterd-geo-rep.c:2685:glusterd_gsync_read_frm_status] 0-: Unable to read gsyncd status file
E [glusterd-geo-rep.c:2999:glusterd_read_status_file] 0-: Unable to read the statusfile for /export/sitedata brick for  ds0(master), 10.42.0.8::geo-repl(slave) session


Expected results:

geo-replication to work.

Additional info:

https://github.com/gluster/glusterfs/blob/release-3.6/geo-replication/src/peer_gsec_create.in#L16

Comment 1 Niels de Vos 2016-06-17 15:56:43 UTC

This bug is getting closed because the 3.5 is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.