Red Hat Bugzilla – Bug 248175
Include maps not working correctly with LDAP
Last modified: 2007-11-16 20:14:56 EST
Description of problem:
I am attempting to include an LDAP map within a file map. The LDAP map is
included, however so are all of our other LDAP maps.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configure /etc/auto.master to use a file map
2. Configure file map to include a LDAP map
Maps other than the desired LDAP map are included.
Only the included LDAP map should be used.
Created attachment 159223 [details]
tgz file with ldif of included map, and other relevant info.
lookup_map_included does this:
ctxt = context_init(map);
which sets up the base dn, as shown in the logs:
Jul 13 12:41:21 houl11 automount: lookup(ldap): server = "(default)", port
= 389, base dn = "automountmapname=auto_int,dc..."
but then we do this:
ctxt->base = NULL;
hmmm. I'll have to give some thought to the reason for this piece of code. In
this case, if we hadn't set the base pointer to NULL, the query would have
worked as desired.
I'll attach a preliminary patch in a few minutes.
Created attachment 159226 [details]
Don't reset the basedn for included maps.
Please give this a try. If you are unable to build packages, then please let
me know what architecture you are running and I will provide packages for you.
Just tried it and it works good. With the patch only the requested map is being
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
A fix for this issue was committed to autofs-4_1_3-225. An RHTS test was added
under /CoreOS/autofs/bugzillas, subtest bz248175.
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.