lowering priority since using /etc/network/interfaces is a workaround.
** Changed in: autofs5 (Ubuntu)
Status: Incomplete = New
** Summary changed:
- ubuntu 12.04 automounts (autofs) not working with ldap maps on boot
+ ldap fails to start when /etc/network/interfaces not used
**
Hello Serge,
I have seen a similar issue with 12.04 installed on a corporate network
that uses LDAP for authentication. As was described in the original bug
posting, automount fails to startup at bootup. When I manually restart
autofs, networked NFS shares are automounted as expected.
I have
Perhaps this is a 'default' configuration issue? My NetworkManager.conf
had managed=false and interfaces had no eth0 entry. I don't know for
sure whether this 'false' setting is an installation artifact or if I
changed it at some point.
The following changes appear to resolve my issue - automount
Thanks for submitting this bug.
The autofs upstart job starts on runlevel 2345, which ensures that
static network configurations are up. Can you show your
/etc/network/interfaces file?
If your /etc/network/interfaces file is empty and you are using
networkmanager to provide network interfaces
Below is the contents of my network interfaces file. As you suspected,
it is empty and I am using network manager to provide network interface
setup for the user, and so I guess the network isn't being brought up
early enough to satisfy autofs.
The network manager has long bothered me. I REALLY
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in Ubuntu.
https://bugs.launchpad.net/bugs/994212
Title:
ubuntu 12.04 automounts (autofs) not working with ldap maps on boot
To manage notifications about this bug go to:
