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.

Bug 1504145

Summary: Automount cannot access host shares after a reboot
Product: Red Hat Enterprise Linux 7 Reporter: Pierguido Lambri <plambri>
Component: autofsAssignee: Ian Kent <ikent>
Status: CLOSED ERRATA QA Contact: xiaoli feng <xifeng>
Severity: high Docs Contact:
Priority: urgent    
Version: 7.4CC: djeffery, igkioka, plambri, swhiteho, xifeng, xzhou
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: autofs-5.0.7-77.el7 Doc Type: Bug Fix
Doc Text:
Due to changes to the master map reading, master map entries were not being initialized properly when a map re-read was needed at startup. This happened due to a mismatch in the master map entry age that used to check if the entry needed to be updated. The entries were not updated properly. As a consequence, autofs ended up with non-functional or partially functional automount mounts. With this update, the master map is now properly read. As a result, the master map is correctly initialized and works correctly after startup.
Story Points: ---
Clone Of:
: 1515311 (view as bug list) Environment:
Last Closed: 2018-04-10 18:17:12 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: 1527815    
Bug Blocks: 1515311    
Attachments:
Description Flags
Patch - reset master map list on startup retry none

Description Pierguido Lambri 2017-10-19 14:38:09 UTC
Description of problem:
After a RHEL 7.4 system is rebooted, the system cannot access the exported shares
of a NFS server using the builtin host maps.

Version-Release number of selected component (if applicable):
autofs-5.0.7-69.el7.x86_64

How reproducible:
So far I've not been able to reproduce it

Steps to Reproduce:
N/A

Actual results:
The system is not able to access the nfs exported shares.

Expected results:
The system should be able to access the NFS exports just after a reboot

Additional info:
A workaround is to restart autofs after the boot.

Comment 16 Ian Kent 2017-10-31 07:07:14 UTC
Created attachment 1345763 [details]
Patch - reset master map list on startup retry

Comment 28 errata-xmlrpc 2018-04-10 18:17:12 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-2018:0977