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 updating from RHEL 7.3 to 7.4, rpcbind is also updated and the new version appears to reintroduce a crash of rpcbind fairly soon after startup in our NFS/NIS environment.

Version-Release number of selected component (if applicable):
0.2.0-42.el7.x86_64

How reproducible:
Every time after upgrade to RHEL 7.4, rpcbind crashes and NIS and NFS fail.

Steps to Reproduce:
1. Boot system
2. Wait less than 10 minutes typically
3. rpcbind will fail

Actual results:
rpcbind fails

Expected results:
rpcbind continues

Additional info:
Downgrading to 0.2.0-38.el7_3.1.x86_64 corrects the problem.  This must be done on both the NFS/NIS servers and clients.

A recent test shows that this is no longer an issue.  I have updated multiple components since then (including the kernel) and so I do not know which caused the problem to no longer exist.  In any case I will close this bug.

(In reply to Andy Feldt from comment #2)
> A recent test shows that this is no longer an issue.  I have updated
> multiple components since then (including the kernel) and so I do not know
> which caused the problem to no longer exist.  In any case I will close this
> bug.

Thank you for your testing!