Bug 1183118

Summary:	Gluster/NFS does not exit cleanly on reboot, leaving rpcbind registrations behind
Product:	[Community] GlusterFS	Reporter:	Niels de Vos <ndevos>
Component:	nfs	Assignee:	bugs <bugs>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	bugs, jthottan, pille+redhat+bugzilla
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-20 06:48:56 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 Niels de Vos 2015-01-16 18:07:15 UTC

Description of problem:
See https://bugzilla.redhat.com/show_bug.cgi?id=1181779#c1

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


How reproducible:
mainline, 3.6 and possibly 3.5

Steps to Reproduce:
1. create a volume and start it (gluster/nfs starts too)
2. reboot
3. after boot, notice that gluster/nfs is not running

Actual results:

[2015-01-16 17:12:48.367304] E [rpcsvc.c:1303:rpcsvc_program_register_portmap] 0-rpc-service: Could not register with portmap 100005 3 38465
[2015-01-16 17:12:48.367350] E [nfs.c:331:nfs_init_versions] 0-nfs: Program  MOUNT3 registration failed
[2015-01-16 17:12:48.367362] E [nfs.c:1342:init] 0-nfs: Failed to initialize protocols
[2015-01-16 17:12:48.367371] E [xlator.c:425:xlator_init] 0-nfs-server: Initialization of volume 'nfs-server' failed, review your volfile again
[2015-01-16 17:12:48.367383] E [graph.c:322:glusterfs_graph_init] 0-nfs-server: initializing translator failed
[2015-01-16 17:12:48.367393] E [graph.c:525:glusterfs_graph_activate] 0-graph: init failed
[2015-01-16 17:12:48.368464] W [glusterfsd.c:1194:cleanup_and_exit] (--> 0-: received signum (0), shutting down


Expected results:

Registration on boot should work. Correctly stopping and unregistering gluster/nfs should prevent this issue.

Additional info:

Comment 1 Jiffin 2018-11-20 06:48:56 UTC

This bug is too old, there is not much development happening in favour of gluster-nfs as well. Hence closing this bug as won't fix