Bug 306701 - autofs version 5 should not require common schema to be pre-configured
autofs version 5 should not require common schema to be pre-configured
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: autofs5 (Show other bugs)
All Linux
low Severity low
: rc
: ---
Assigned To: Ian Kent
: Regression, Reopened
Depends On: 306681
  Show dependency treegraph
Reported: 2007-09-26 06:30 EDT by Ian Kent
Modified: 2008-07-24 15:08 EDT (History)
2 users (show)

See Also:
Fixed In Version: RHBA-2008-0659
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-07-24 15:08:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ian Kent 2007-09-26 06:30:19 EDT
+++ This bug was initially created as a clone of Bug #306681 +++

Description of problem:
In autofs version 5, to reduce the number of queries to an
LDAP server being used for autofs maps, the schema used needs
to be specified in the configuration. But in RHEL 4 the common
schema are checked by the daemon when reading maps and performing

This has proven to be a source of confusion for people updating
from version 4 to version 5 needs to be fixed in autofs verion5.
Comment 1 RHEL Product and Program Management 2007-09-26 06:34:27 EDT
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 2 Ian Kent 2008-03-18 00:10:21 EDT
The RHTS sub test bz196111 under autofs-tests/bugzillas can
be used to verify this bug.

This issue is fixed in autofs5-5.0.1-0.rc2.87.
Comment 4 Barry Donahue 2008-06-12 09:35:36 EDT
Verified RHTS job #23575
Comment 6 errata-xmlrpc 2008-07-24 15:08:43 EDT
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 therefore 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.


Note You need to log in before you can comment on or make changes to this bug.