Bug 1440064

Summary:	gluster nfs-ganesh enable fails to create symlink
Product:	[Community] GlusterFS	Reporter:	Mark Gerrits <sjonge>
Component:	ganesha-nfs	Assignee:	Kaleb KEITHLEY <kkeithle>
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.10	CC:	bugs, jthottan, kkeithle, skoduri
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Linux
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:29:19 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 Mark Gerrits 2017-04-07 09:02:13 UTC

Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Create a 3 node gluster 3.10 cluster on Ubuntu 16.04 (ppa source)
2. Place ganesha config files on shared storage
3. run gluster nfs-ganesh enable

Actual results:

The 'enable' command fails with :

Enabling NFS-Ganesha requires Gluster-NFS to be disabled across the trusted pool. Do you still want to continue?
 (y/n) y
This will take a few minutes to complete. Please wait ..
nfs-ganesha: failed: creation of symlink ganesha.conf in /etc/ganesha failed


relevant gluster log file entries :

https://gist.github.com/skinny/348b940ae974d20fa8e3e2120eec332e


Expected results:

ganesha enabled :)


Additional info:

Running the ganesha-ha.sh script with the arguments as constructed in the gluster source works fine (and actually creates/removes the symlink as requested). 

Based on IRC chats this might have something to do with glusterd not able to find the ganesha-ha.sh script because ubuntu doesn't have the /libexec folder.

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

Comment 1 Shyamsundar 2018-06-20 18:29:19 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.