Bug 1420574

Summary: Trying to access a non-existent directory using automount results in 4 minute hang as not checking the local mount availability [rhel-7]
Product: Red Hat Enterprise Linux 7 Reporter: Ian Kent <ikent>
Component: autofsAssignee: Ian Kent <ikent>
Status: CLOSED ERRATA QA Contact: Yongcheng Yang <yoyang>
Severity: medium Docs Contact: Milan Navratil <mnavrati>
Priority: high    
Version: 7.3CC: ajmitchell, bcodding, bfields, chunwang, eguan, fs-qe, ikent, steved, swhiteho, tlavigne, yoyang
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: autofs-5.0.7-58.el7 Doc Type: Bug Fix
Doc Text:
Checking local mount availability with *autofs* no longer leads to a lengthy timeout before failing Previously, a server availability probe was not done for mount requests that *autofs* considered local because a bind mount on the local machine is expected to be available for use. If the bind mount failed, an NFS mount on the local machine was then tried. However, if the NFS server was not running on the local machine, the mount attempt sometimes suffered a lengthy timeout before failing. An availability probe has been added to the case where a bind mount is first tried, but fails, and *autofs* now falls back to trying to use an NFS server on the local machine. As a result, if a bind mount on the local machine fails, the fallback to trying an NFS mount on the local machine fails quickly if the local NFS server is not running.
 Story Points: ---
Clone Of: 1396403 Environment:
Last Closed: 2017-08-01 12:43:52 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:
Bug Depends On: 1396403    
Bug Blocks:    

Comment 6 Yongcheng Yang 2017-06-16 05:31:44 UTC 
The patch mentioned in Bug 1396403 comment #24 has already been
merged and no more issue is found during the regression tests.

As this problem cannot be reproduced, just verify it as "SanityOnly".
Comment 7 errata-xmlrpc 2017-08-01 12:43:52 UTC 
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://access.redhat.com/errata/RHBA-2017:2213