Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Cause:
A server availability probe is not done for mount requests that autofs thinks are local because a bind mount on the local machine should be able to be used. If the bind mount fails an NFS mount on the local machine then tried.
Consequence:
But if the NFS server is not running on the local machine the mount attempt can suffer a lengthy time out before failing.
Fix:
To resolve this an availability probe has been added to the case where a bind mount is first tried but fails and autofs falls back to trying to use an NFS server on the local machine.
Result:
If a bind mount on the local machine fails the fall back to trying an NFS mount on the local machine fails quickly if the local NFS server is not running.
Comment 13Steve Whitehouse
2017-01-05 15:15:24 UTC
We need to figure out a solution here fairly soon, since time is limited to make changes in 6.9. Is this really a regression?
Steve D / Ian what is the lowest risk option that is open to us?
(In reply to Steve Whitehouse from comment #13)
> We need to figure out a solution here fairly soon, since time is limited to
> make changes in 6.9. Is this really a regression?
>
> Steve D / Ian what is the lowest risk option that is open to us?
I think mount.nfs(8) needs work but I also can't leave autofs
open to this.
I should be able to add RPC ping check for this special case
alone without much effort and since the mount ultimately fails
it shouldn't introduce a regression.
I'll do that.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2017-0780.html