Red Hat Bugzilla – Bug 478717
Static /etc/hosts entries ignored after update to 5.3
Last modified: 2009-01-05 11:38:53 EST
Description of problem:
Autofs ignores static host entries in /etc/hosts after the update to 5.3
Steps to Reproduce:
1. Create a know-to work /etc/hosts file on a 5.3 installation (or update a working 5.2 machine to 5.3).
2. Make sure to add a hostname for a test nfs server that does not otherwise resolve (through DNS).
3. Configure autofs to use the hosts map for the /net path (default)
4. Verify that the IP address is pingable and that
5. Verify that automount can access the test server under its ip address (ls /net/IP/)
6. Try to access the test server under it's name defined in /etc/hosts (ls /net/NAME/)
ls reports "No such file or directory" and /var/log/messages contains:
automount[PID]: create_udp_client:90: hostname lookup failed: Operation not permitted
automount[PID]: create_tcp_client:299: hostname lookup failed: Operation not permitted
automount[PID]: lookup_mount: exports lookup failed for HOST
Ls lists the exported directories as it does when using the IP address.
A similar issue seems to exist with ping (bug 478716), while ssh, wget, curl, elinks, traceroute or telnet are not affected.
Opening against autofs as it does not affect most other users of libresolv.
The original issue was seen in a Xen guest on x86_64. The issues does not show in i386 bare metal.
SELinux was in permissive mode on the x86_64 Xen guest where this issue was
seen and in enforcing mode on the i386 bare metal machine where it did not
reproduce. So it does not seem to be a factor.
showmount -e shows the same issue and might be the underlying cause: it is called from auto.net to find the exports from the server and calling it separately creates the same log messages.
Please include your auto.master. In autofs version 5, you should not be using the auto.net script. The line in auto.master should instead read:
Please also include your /etc/nsswitch.conf file.
Seems like a NSCD related thing, at least the ping bug, see
ACK. Stopping NSCD workes around the issue.
OK, reassigning to glibc. Please feel free to throw it back over the fence (with the requested configuration files) if the issue is not with nscd.
Closing dupe against bug 478716 as it seems to be the same underlying nscd issue.
*** This bug has been marked as a duplicate of bug 478716 ***