Bug 819940

Summary:	Cannot mount NFS Version 3 after RPCBIND restart
Product:	Red Hat Enterprise Linux 6	Reporter:	Jay Vasa <jvasa>
Component:	rpcbind	Assignee:	Steve Dickson <steved>
Status:	CLOSED NOTABUG	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.4	CC:	rwheeler, syeghiay
Target Milestone:	rc
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-28 13:02:28 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 Jay Vasa 2012-05-08 16:35:44 UTC

Description of problem:

When service "nfsd" and "rpcbind" is running, and I do a restart of "rpcbind", nfs clients mounting nfs version 3 shares are given the message:
"mount.nfs: requested NFS version or transport protocol is not supported"


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

nfs-utils-1.2.3-15.el6.i686


How reproducible:

Just restart rpcbind when nfsd service is running

Steps to Reproduce:
1. service rpcbind start; service nfs start
2. service rpcbind restart
3. on client: mount -t nfs -o nfsvers=3 server:/mountpoint /mnt/mnt

  
Actual results:
Client says:
"mount.nfs: requested NFS version or transport protocol is not supported"


Expected results:
Should be able to mount

Additional info:

Work around is to restart nfsd after rpcbind is restarted.
So after restarting rpcbind, I have to do the command:
% service nfs restart
(this shouldn't have to happen)

Comment 2 RHEL Program Management 2012-05-12 04:13:40 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 Steve Dickson 2012-05-21 13:39:45 UTC

> Expected results:
> Should be able to mount
> 
> Additional info:
> 
> Work around is to restart nfsd after rpcbind is restarted.
> So after restarting rpcbind, I have to do the command:
> % service nfs restart
> (this shouldn't have to happen)
Why? How are the rpc.mountd and rpc.statd daemons suppose to know to
re-register their port with rpcbind after the restart?