Bug 574303

Summary: RFE: Add locality LDAP attribute to
Product: [Fedora] Fedora Reporter: Ian Kent <ikent>
Component: autofsAssignee: Ian Kent <ikent>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 13CC: blimus, ikent, jmoyer
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: autofs-5.0.5-22.fc13 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 566481 Environment:
Last Closed: 2010-03-18 03:23:34 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: 538274    

Description Ian Kent 2010-03-17 05:31:11 UTC
+++ This bug was initially created as a clone of Bug #566481 +++

Description of problem:

autofs can't use an automount LDAP DN using the l (localityName) attribute. With 

Entry in /etc/auto.master:

/home  ldap:automountMapName=auto_home,l=sanjose,ou=labs,dc=example,dc=com

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

How reproducible:
Always

Steps to Reproduce:
1. Add an automount map to LDAP using the localityName attribute
2. Point an entry in /etc/auto.master to your DN

Additional info:

With LOGGING set to debug, I see the following in /var/log/messages regarding the LDAP DN with localityName :

Feb 18 00:18:03 redhat automount[2838]: lookup_nss_read_master: reading master files auto.master
Feb 18 00:18:03 redhat automount[2838]: parse_init: parse(sun): init gathered global options: (null)
Feb 18 00:18:03 redhat automount[2838]: lookup_read_master: lookup(file): read entry /misc
Feb 18 00:18:03 redhat automount[2838]: lookup_read_master: lookup(file): read entry /net
Feb 18 00:18:03 redhat automount[2838]: lookup_read_master: lookup(file): read entry /home
Feb 18 00:18:03 redhat automount[2838]: syntax error in map near [ l ]

--- Additional comment from ikent on 2010-02-25 10:48:34 EST ---

I have built a package with a patch that might resolve this
issue. It can be found at:
http://people.redhat.com/~ikent/autofs-5.0.1-0.rc2.140.bz566481.1.el5

I haven't tested the change at all but if you want to test it out
on a test machine please do, otherwise you'll need to wait until
I get time to setup a test environment and do some tests.

--- Additional comment from blimus on 2010-02-25 12:40:14 EST ---

(In reply to comment #1)
> I have built a package with a patch that might resolve this
> issue. It can be found at:
> http://people.redhat.com/~ikent/autofs-5.0.1-0.rc2.140.bz566481.1.el5

The test RPM works in my test environment. The syntax error is gone and I now have a working automounter - thanks!

--- Additional comment from ikent on 2010-02-25 20:57:33 EST ---

(In reply to comment #2)
> (In reply to comment #1)
> > I have built a package with a patch that might resolve this
> > issue. It can be found at:
> > http://people.redhat.com/~ikent/autofs-5.0.1-0.rc2.140.bz566481.1.el5
> 
> The test RPM works in my test environment. The syntax error is gone and I now
> have a working automounter - thanks!    

Thanks, I'll do some testing, when I get a chance, to see if it
breaks anything else.

Comment 1 Fedora Update System 2010-03-17 05:41:34 UTC
autofs-5.0.5-22.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/autofs-5.0.5-22.fc13

Comment 2 Fedora Update System 2010-03-17 05:59:12 UTC
autofs-5.0.5-22.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/autofs-5.0.5-22.fc12

Comment 3 Fedora Update System 2010-03-18 03:23:04 UTC
autofs-5.0.5-22.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 4 Fedora Update System 2010-03-18 03:32:35 UTC
autofs-5.0.5-22.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.