Bug 1294446

Summary:	Ganesha hook script executes showmount and causes a hang
Product:	[Community] GlusterFS	Reporter:	Niels de Vos <ndevos>
Component:	ganesha-nfs	Assignee:	Niels de Vos <ndevos>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, kkeithle
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1297862 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:52:16 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:
Bug Depends On:
Bug Blocks:	1297862

Description Niels de Vos 2015-12-28 08:37:08 UTC

Description of problem:
When rpcbind is not running on the server (or is firewalled), and a Gluster volume is started (after create or stop), a hook script calls 'showmount' and hangs.

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

How reproducible:
100%

Steps to Reproduce (from memory):
1. stop the rpcbind service (also rpcbind.sock on systemd based installations)
2. create a volume
3. set the 'ganesha.enable' volume option
4. start the volume

Actual results:
The 'gluster volume star ...' command hangs, 

Expected results:
No hang.

Additional info:
The cause seems to be the 'S31ganesha-start.sh' hook script. Instead of 'showmount', an equivalent dbus command could be used.

Comment 1 Vijay Bellur 2015-12-28 09:40:26 UTC

REVIEW: http://review.gluster.org/13098 (scripts: prevent running 'showmount' from the start/post hook script) posted (#1) for review on master by Niels de Vos (ndevos)

Comment 2 Niels de Vos 2015-12-28 09:54:58 UTC

(In reply to Niels de Vos from comment #0)
...
> Steps to Reproduce (from memory):
> 1. stop the rpcbind service (also rpcbind.sock on systemd based
> installations)
> 2. create a volume
> 3. set the 'ganesha.enable' volume option
> 4. start the volume

It does not seem to be required to set the 'ganesha.enable' volume option. The 'showmount' command that hangs, is executed before this option is checked.

Comment 3 Vijay Bellur 2015-12-28 13:56:50 UTC

REVIEW: http://review.gluster.org/13098 (scripts: prevent running 'showmount' from the start/post hook script) posted (#2) for review on master by Niels de Vos (ndevos)

Comment 4 Vijay Bellur 2015-12-29 19:37:16 UTC

REVIEW: http://review.gluster.org/13098 (scripts: prevent running 'showmount' from the start/post hook script) posted (#3) for review on master by Niels de Vos (ndevos)

Comment 5 Vijay Bellur 2016-01-12 09:05:59 UTC

REVIEW: http://review.gluster.org/13098 (scripts: prevent running 'showmount' from the start/post hook script) posted (#4) for review on master by Niels de Vos (ndevos)

Comment 6 Vijay Bellur 2016-01-12 15:38:35 UTC

COMMIT: http://review.gluster.org/13098 committed in master by Kaleb KEITHLEY (kkeithle) 
------
commit 2b2294d2a4ef221fccb6eb9f74e9b7dc233b9f1d
Author: Niels de Vos <ndevos>
Date:   Mon Dec 28 10:26:20 2015 +0100

    scripts: prevent running 'showmount' from the start/post hook script
    
    The 31ganesha-start.sh hook script tries to run 'showmount' to see if
    the volume that is getting started should get exported by NFS-Ganesha.
    It was reported that this caused the 'gluster volume start ...' command
    to hang in case rpcbind is not running.
    
    Instead of running 'showmount', we can use DBus to contact NFS-Ganesha
    directly, and request the available exports. This will immediately fail
    in case NFS-Ganesha is not running.
    
    BUG: 1294446
    Change-Id: I3aba1f86fead67116ca5adb1864a8be626c334fa
    Reported-by: Jeff Darcy <jdarcy>
    Signed-off-by: Niels de Vos <ndevos>
    Reviewed-on: http://review.gluster.org/13098
    Tested-by: Raghavendra Talur <rtalur>
    Reviewed-by: jiffin tony Thottan <jthottan>
    Reviewed-by: Kaleb KEITHLEY <kkeithle>

Comment 7 Niels de Vos 2016-06-16 13:52:16 UTC

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.0, please open a new bug report.

glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user