+++ This bug was initially created as a clone of Bug #1430844 +++ +++ This bug was initially created as a clone of Bug #1430841 +++ Description of problem: GLUSTERFS_LIBEXECDIR is effectively hard-coded to /usr/libexec/glusterfs in configure(.ac) Debian-based distributions don't have a /usr/libexec/ directory This issues is partially mitigated by the use of $libexecdir in some of the Makefile.am files, but even so the incorrectly defined GLUSTERFS_LIBEXECDIR results in various things such as gsyncd, glusterfind, eventsd, etc., trying to invoke other scripts and programs from a location that doesn't exist. And once we correctly define GLUSTERFS_LIBEXECDIR, then we might as well use it appropriatedly. Version-Release number of selected component (if applicable): all How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/16882 (build/packaging: Debian and Ubuntu don't have /usr/libexec) posted (#1) for review on release-3.8 by Kaleb KEITHLEY (kkeithle)
REVIEW: https://review.gluster.org/16882 (build/packaging: Debian and Ubuntu don't have /usr/libexec) posted (#2) for review on release-3.8 by Kaleb KEITHLEY (kkeithle)
REVIEW: https://review.gluster.org/16882 (build/packaging: Debian and Ubuntu don't have /usr/libexec) posted (#3) for review on release-3.8 by Kaleb KEITHLEY (kkeithle)
COMMIT: https://review.gluster.org/16882 committed in release-3.8 by Kaleb KEITHLEY (kkeithle) ------ commit d772a79d6fac46426b5eaa6a307bac74f4e8033f Author: Kaleb S. KEITHLEY <kkeithle> Date: Thu Mar 9 12:34:41 2017 -0500 build/packaging: Debian and Ubuntu don't have /usr/libexec GLUSTERFS_LIBEXECDIR is effectively hard-coded to /usr/libexec/glusterfs in configure(.ac) Debian-based distributions don't have a /usr/libexec/ directory This issues is partially mitigated by the use of $libexecdir in some of the Makefile.am files, but even so the incorrectly defined GLUSTERFS_LIBEXECDIR results in various things such as gsyncd, glusterfind, eventsd, etc., trying to invoke other scripts and programs from a location that doesn't exist. And once we correctly define GLUSTERFS_LIBEXECDIR, then we might as well use it appropriatedly. master change https://review.gluster.org/16880 master BZ: 1430841 release-3.10 change https://review.gluster.org/16881 release-3.10 BZ: 1430845 Change-Id: If5219cadc51ae316f7ba2e2831d739235c77902d BUG: 1430845 Signed-off-by: Kaleb S. KEITHLEY <kkeithle> Reviewed-on: https://review.gluster.org/16882 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Milind Changire <mchangir>
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-3.8.11, please open a new bug report. glusterfs-3.8.11 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] http://lists.gluster.org/pipermail/packaging/2017-April/000289.html [2] https://www.gluster.org/pipermail/gluster-users/