Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #783496 +++
++Same behavior observed on RHEL 6.2, autofs-5.0.5-39.el6
Created attachment 556544[details]
ldif with comments
Description of problem:
We have "nested" automount maps and those worked under autofs-5.0.6-2.fc16 but now fail under autofs-5.0.6-4.fc16 with the message "validate_location: expected colon delimeter not found in location ou=auto.project,..."
Version-Release number of selected component (if applicable):
autofs-5.0.6-4.fc16
How reproducible:
Happens every time
Steps to Reproduce:
The ldap setup is in an attached file.
Actual results:
autofs-5.0.6-4.fc16
automount[23977]: attempting to mount entry /var/phy/project
automount[23977]: validate_location: expected colon delimeter not found in location ou=auto.project,dc=phy,dc=duke,dc=edu
automount[23977]: failed to mount /var/phy/project
Expected results:
autofs-5.0.6-2.fc16
automount[24196]: attempting to mount entry /var/phy/project
automount[24196]: file map /etc/ou=auto.project,dc=phy,dc=duke,dc=edu not found
automount[24196]: mounted indirect on /var/phy/project with timeout 300, freq 75 seconds
automount[24196]: mounted /var/phy/project
automount[24196]: attempting to mount entry /var/phy/project/linux
automount[24196]: mounted /var/phy/project/linux
Additional info:
--- Additional comment from jdorff.edu on 2012-01-20 13:47:26 EST ---
It seems that adding a ":" to the automountInformation field helps.
In my case "automountInformation: -fstype=autofs :ou=auto.project,..."
--- Additional comment from ikent on 2012-01-22 18:59:41 EST ---
Created attachment 556833[details]
Patch - fix improve mount location error reporting
--- Additional comment from updates on 2012-01-22 19:01:21 EST ---
autofs-5.0.6-5.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/autofs-5.0.6-5.fc16
--- Additional comment from updates on 2012-01-23 17:02:08 EST ---
Package autofs-5.0.6-5.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing autofs-5.0.6-5.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-0842/autofs-5.0.6-5.fc16
then log in and leave karma (feedback).
This is a duplicate of bug 772356.
Unfortunately, that bug has been marked private and I don't
want to change that as it was probably done for a specific
reason. Perhaps if you had logged the problem through the
normal support mechanism things would be different.
Anyway, I'm going to close this as a duplicate.
If you wish to be added to that bug then you will need to
log the call via support.
*** This bug has been marked as a duplicate of bug 772356 ***