Bug 1452761 - geo-replication and similar hooks should probably reside in exec_prefix
Summary: geo-replication and similar hooks should probably reside in exec_prefix
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: scripts
Version: 3.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Aravinda VK
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-19 14:52 UTC by nh2
Modified: 2018-06-20 18:24 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-06-20 18:24:24 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description nh2 2017-05-19 14:52:32 UTC
Description of problem:

Currently GlusterFS expects all hooks, including those that are required for correct operation and not really intended to be user-modifiable (such as the geo-replication hooks that come with gluster), in /var/lib/glusterd/hooks/.

It is unusual for a build system to place its own files required for correct operation into /var as opposed to a read-only location under PREFIX.

In practice, this makes it hard to package gluster for distributions that enforce a strict separation between package provided files and user-managed run-time files, such as NixOS, where packages are not allowed at build-time to place things into `/var`.

JoeJulian and I believe these inbuilt hooks should reside under exec_prefix, like the other scripts required for geo-replication.

(If those hooks are also intended to be user-modifiable, the best solution seems to be to deliver the "default" version in exec_prefix, but check at run-time if the user has overridden them with their own scripts in /var.)

Comment 1 Shyamsundar 2018-06-20 18:24:24 UTC
This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained.

As a result this bug is being closed.

If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately.


Note You need to log in before you can comment on or make changes to this bug.