Bug 761330

Summary: autofs doesn't work via systemctl with latest update
Product: [Fedora] Fedora Reporter: Ben Boeckel <fedora>
Component: autofsAssignee: Ian Kent <ikent>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: ikent
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-08 14:44:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ben Boeckel 2011-12-08 04:04:50 UTC
Description of problem:
Autofs starts, but does not drop a pid file and mounts do not work. Manually starting automount with the `-f` flag works, but backgrounding does not. The pid file gets created in this case. When started with systemctl, it does not.

Things were working, then once the update was complete, all of the mounts disappeared and would not come back.

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

Nov 09 00:12:16 Updated: 1:autofs-5.0.6-3.fc17.x86_64 (working)
Dec 07 22:36:47 Updated: 1:autofs-5.0.6-5.fc17.x86_64 (broken)

Running kernel:

kernel-3.2.0-0.rc4.git1.4.fc17.x86_64

Just installed (untested):

kernel-3.2.0-0.rc4.git4.2.fc17.x86_64

How reproducible:
Always so far.

Comment 1 Ian Kent 2011-12-08 14:44:03 UTC
(In reply to comment #0)
> Description of problem:
> Autofs starts, but does not drop a pid file and mounts do not work. Manually
> starting automount with the `-f` flag works, but backgrounding does not. The
> pid file gets created in this case. When started with systemctl, it does not.
> 
> Things were working, then once the update was complete, all of the mounts
> disappeared and would not come back.
> 
> Version-Release number of selected component (if applicable):
> yum.log:
> 
> Nov 09 00:12:16 Updated: 1:autofs-5.0.6-3.fc17.x86_64 (working)
> Dec 07 22:36:47 Updated: 1:autofs-5.0.6-5.fc17.x86_64 (broken)
> 
> Running kernel:
> 
> kernel-3.2.0-0.rc4.git1.4.fc17.x86_64
> 
> Just installed (untested):
> 
> kernel-3.2.0-0.rc4.git4.2.fc17.x86_64
> 
> How reproducible:
> Always so far.

Yes, I just discovered it myself.
I've been working on it today and I'm nearly done.

We'll track this via bug 754421, so I'll mark this as a duplicate.

Ian

*** This bug has been marked as a duplicate of bug 754421 ***