Bug 136901 - autofs failure to mount when using wild card in entry and ldap
Summary: autofs failure to mount when using wild card in entry and ldap
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Final
Hardware: i686 SuSE Linux 10.0
: P2 - High : Major
Target Milestone: ---
Assignee: Chris L Mason
QA Contact: E-mail List
URL:
Whiteboard:
Keywords: Backwards_Compatibility
Depends on:
Blocks:
 
Reported: 2005-12-05 13:54 UTC by Sean Ellicott
Modified: 2006-08-14 07:12 UTC (History)
0 users

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sean Ellicott 2005-12-05 13:54:45 UTC
autofs is not able to succesfully find and/or
match usernames to automount map enties when
configured to read maps from an ldapserver and the
map entry contains a wildcard 

i.e. servername:/home/&

where the "&" should represent the user name

The logs indicate the automount process is unable
to find a coresponding map entry.

This behavior is different than the behavior of
autofs4-4.1.3-8.rpm (from SuSE 9.3)which works
using the same map entries.


_22-Other_Product: standard suse 10.0 with a default KDE install
Open Ldap Server
_23-Steps: Compared a standard SuSE 9.3 install agains a standard SuSE10 install.

both were configured to use LDAP for Authentication and set to have the automounter start

The SuSE 9.3 install would automount the home directory.

The SuSE 10.0 install would not automount the home directory.
_24-Other_Scenarios: Didn't try others
_25-Environment_Description: One production NFS server running SLES 9sp2
One Production Ldap Server Running SLES 9 sp2 and
OpenLDAP

One work station Running SuSE 10 configured to use
ldap and automount

We currently have many suse 9.3 prof boxes running
off this environment using the same configuration.
The Suse 10 box was to be tested and if it worked
we were to upgrade all boxes to suse 10.
Comment 1 Sean Ellicott 2005-12-05 13:58:18 UTC
i substituted the older autofs rpm for the one included on suse 10 and then suse 10 worked fine. the problem is with the rmp package included in suse 10.
Comment 2 Olaf Kirch 2005-12-05 14:18:26 UTC
This is not a kernel issue, it's in the autofs user land.
Comment 3 Greg Kroah-Hartman 2006-08-14 07:12:03 UTC
Closed due to inactivity.