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/16880 (build/packaging: Debian and Ubuntu don't have /usr/libexec) posted (#1) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: https://review.gluster.org/16880 (build/packaging: Debian and Ubuntu don't have /usr/libexec) posted (#2) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: https://review.gluster.org/16880 (build/packaging: Debian and Ubuntu don't have /usr/libexec) posted (#3) for review on master by Kaleb KEITHLEY (kkeithle)
COMMIT: https://review.gluster.org/16880 committed in master by Shyamsundar Ranganathan (srangana) ------ commit fdabb97d57793084190440b90c75c37761d5720c Author: Kaleb S. KEITHLEY <kkeithle> Date: Thu Mar 9 12:18:40 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. Change-Id: If5219cadc51ae316f7ba2e2831d739235c77902d BUG: 1430841 Signed-off-by: Kaleb S. KEITHLEY <kkeithle> Reviewed-on: https://review.gluster.org/16880 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> Reviewed-by: Joe Julian <me> Reviewed-by: Shyamsundar Ranganathan <srangana>
The packages are still bad, see Bug 1444228 and in particular the "Additional info" section.
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.11.0, please open a new bug report. glusterfs-3.11.0 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/announce/2017-May/000073.html [2] https://www.gluster.org/pipermail/gluster-users/