Bug 332291

Summary: autofs fails if nsswitch.conf doesn't have automount entry
Product: Red Hat Enterprise Linux 5 Reporter: Ian Kent <ikent>
Component: autofsAssignee: Ian Kent <ikent>
Status: CLOSED ERRATA QA Contact: Brock Organ <borgan>
Severity: low Docs Contact:
Priority: low    
Version: 5.0CC: ikent, jmoyer
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2008-0354 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-21 14:38: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:
Bug Depends On:    
Bug Blocks: 425883, 429340    
Attachments:
Description Flags
Patch to use "files" source if nsswitch dosn't specify an explicit map source none

Description Ian Kent 2007-10-15 13:35:06 UTC
Description of problem:

If /etc/nsswitch.conf doesn't have an entry for automount
autofs fails to start.

Version-Release number of selected component (if applicable):
autofs-5.0.2-0.rc2.43.

How reproducible:
Always.

Steps to Reproduce:
Remove the line starting with "automount:" from
/etc/nsswitch.conf and try and start autofs.
  
Actual results:
autofs fails to start.

Expected results:
autofs should use files as the source of maps if there is
no entry in the nsswitch configuration.

Comment 1 Ian Kent 2007-10-15 13:35:06 UTC
Created attachment 227671 [details]
Patch to use "files" source if nsswitch dosn't specify an explicit map source

Comment 2 RHEL Program Management 2007-10-15 13:45:43 UTC
This bugzilla has Keywords: Regression.  

Since no regressions are allowed between releases, 
it is also being proposed as a blocker for this release.  

Please resolve ASAP.

Comment 9 errata-xmlrpc 2008-05-21 14:38:03 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2008-0354.html