RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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)

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.

> 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?