Bug 744480

Summary:	/net directory not created on boot
Product:	[Fedora] Fedora	Reporter:	Bill C. Riemers <briemers>
Component:	autofs	Assignee:	Ian Kent <ikent>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	15	CC:	ikent
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-07 16:23:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Bill C. Riemers 2011-10-08 22:48:46 UTC

Description of problem:

When I start up Fedora 15 autofs is successfully started, but the /net directory does not exist.   If after booting I do:
   service autofs stop
   service autofs start

There is about 70% chance the /net directory will appear.  If not I simply repeat the procedure until it does appear.


Version-Release number of selected component (if applicable):

5.0.5-38

How reproducible:

100% on boot

Steps to Reproduce:
1. make sure /etc/auto.master contains:
 /net	-hosts
2. reboot
3. from a terminal window do "ls -la /net"

  
Actual results:

ls: cannot access /net: No such file or directory

Expected results:

An empty directory list, or a listing of mounts.

Additional info:

This problem actually started occurring in Fedora 15, but then it was a rare occurrence rather than every boot.   Presumably a workaround would be a crontab that restarted autofs if /net does not exist.  I find actually doing a service autofs stop and service autofs start is successful more often than a service autofs restart.  Perhaps the delay between typing the commands aids in recovery.

Comment 1 Ian Kent 2011-10-10 03:07:19 UTC

Can you provide a debug log please.

Set LOGGING="debug" in /etc/sysconfig/autofs and ensure that
syslog is logging daemon.*.

Comment 2 Bill C. Riemers 2011-12-12 13:27:52 UTC

This problem has been resolved in fedora 16.

Comment 3 Fedora End Of Life 2012-08-07 16:23:31 UTC

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping