Bug 1452761

Summary:	geo-replication and similar hooks should probably reside in exec_prefix
Product:	[Community] GlusterFS	Reporter:	nh2 <nh2-redhatbugzilla>
Component:	scripts	Assignee:	Aravinda VK <avishwan>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.10	CC:	bugs, khiremat, nh2-redhatbugzilla
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-20 18:24:24 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 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.