[Bug 1101779] Re: autofs "lookup_mount: exports lookup" fails on IPv6-only hosts

[Andreas Hasenack]

Correct. We need to bring in the newer libtirpc, then we can link autofs
with it and fix this bug here about ipv6 support.

As of now, ubuntu cosmic has libtirpc-0.2.5-1.2 (old), and debian has
1.0.2-0.2 in experimental. That's a bit better than how it was a while
ago, when debian had a new source package for the newer libtirpc called
libtirpc3. I think that was because of the transition.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1101779

Title:
  autofs "lookup_mount: exports lookup" fails on IPv6-only hosts

Status in autofs package in Ubuntu:
  Confirmed
Status in Debian:
  New
Status in Fedora:
  Fix Released

Bug description:
  Using Linux Mint 14 and both autofs 5.0.6 and 5.0.7, when attempting to access an NFS server mounted under /net with an auto.master configuration such as:
  /net -hosts

  If the host is only accessible over IPv6 (i.e. it only has an AAAA record in DNS, or there is no accessible A address), attempting to 'cd' to its host name (e.g. "cd /net/server") will timeout after a few seconds (bash: cd: server: No such file or directory) and result in a syslog entry similar to:
  Jan 19 22:39:43 client automount[5582]: lookup_mount: exports lookup failed for server

  Immediately upon adding an accessible A (IPv4) address for the server,
  everything will work correctly (and NFS mounts created by autofs will
  continue to use the IPv6 address by default).

  It appears that the rpc_get_exports() function in autofs is not
  correctly defaulting to IPv6 when it is available, even though NFS
  will default to IPv6, and is failing when the server is not accessible
  over IPv4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1101779/+subscriptions