Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1632013

Summary:	georep: hard-coded paths in gsyncd.conf.in
Product:	[Community] GlusterFS	Reporter:	Kaleb KEITHLEY <kkeithle>
Component:	geo-replication	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1	CC:	bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-4.1.6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-29 15:25:05 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:

Description Kaleb KEITHLEY 2018-09-23 10:38:29 UTC

Description of problem:

backport from master

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Kaleb KEITHLEY 2018-09-23 10:39:36 UTC

Change-Id: I6523894416cc06236ea1f99529efd36e957bd98e

Comment 2 Kaleb KEITHLEY 2018-09-23 10:39:54 UTC

https://review.gluster.org/c/glusterfs/+/21246

Comment 3 Worker Ant 2018-09-23 10:41:35 UTC

REVIEW: https://review.gluster.org/21246 (georep: fix hard-coded paths in gsyncd.conf.in) posted (#2) for review on release-4.1 by Kaleb KEITHLEY

Comment 4 Worker Ant 2018-09-24 13:55:29 UTC

COMMIT: https://review.gluster.org/21246 committed in release-4.1 by "Kaleb KEITHLEY" <kkeithle> with a commit message- georep: fix hard-coded paths in gsyncd.conf.in

This is part of the reason why we use autoconf (i.e. configure).
For an ordinary clone+autogen.sh+configure SBIN_DIR is
/usr/local/sbin; for an rpm or dpkg build it will be /usr/sbin.

I wonder how many more are lurking in our sources? /usr/libexec is
one that frequently bites us on  Debian and Ubuntu, which don't have
/usr/libexec. (But it's all Linux, right?)

See https://bugzilla.redhat.com/show_bug.cgi?id=1601532

Reported-by: lohmaier+rhbz
Change-Id: I6523894416cc06236ea1f99529efd36e957bd98e
updates: bz#1632013
Signed-off-by: Kaleb S. KEITHLEY <kkeithle>

Comment 5 Shyamsundar 2018-11-29 15:25:05 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-4.1.6, please open a new bug report.

glusterfs-4.1.6 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-November/000116.html
[2] https://www.gluster.org/pipermail/gluster-users/