[Bug 1970264] Re: autofs fails to mount nfs4 shares with "error 0x3 getting portmap client"

[Sergio Durigan Junior]

First of all, thank you for taking the time to report this bug.

Indeed, the email thread you linked seems to be related to what you're
seeing.  I have been trying to reproduce the problem locally, but so far
I haven't been able to.  I'm not using a complex setup like yours; I've
just configured a NFS share and setup autofs to automount it, everything
in the same VM.  Then, I forced nfs-server to use NFSv4 only, edited its
systemd service file to not depend on rpcbind, and masked/stopped
rpcbind.{service,socket}.  Even then I was still able to automount the
share successfully.

I'm going to continue investigating tomorrow, but if you have a quick
reproducer there I'd appreciate.  We will need it in order to proceed
with SRU process.

Thanks in advance.

** Also affects: autofs (Ubuntu Kinetic)
   Importance: Undecided
       Status: New

** Also affects: autofs (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Tags added: server-todo

** Changed in: autofs (Ubuntu Jammy)
     Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

** Changed in: autofs (Ubuntu Kinetic)
     Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

-- 
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/1970264

Title:
  autofs fails to mount nfs4 shares with "error 0x3 getting portmap
  client"

Status in autofs package in Ubuntu:
  New
Status in autofs source package in Jammy:
  New
Status in autofs source package in Kinetic:
  New

Bug description:
  I'm running a server which provides user home directories as NFSv4
  shares. The clients mount these shares via automount + LDAP.

  Now I've updated one client from 20.04 to 22.04 (new installation from scratch). Setting up things as before, I cannot get the home directories to mount properly. The LDAP connection does work, and also manual mounting of the NFSv4 shares works. So the problem is in the automount part of the mechanism.
  The autofs package version on the 22.04 client is 5.1.8-1ubuntu1.

  Setting autofs to verbose mode, I get the following lines in /var/log/syslog on the client.
  automount[115692]: mount(nfs): nfs options="nfsvers=4,hard", nobind=0, nosymlink=0, ro=0
  automount[115692]: get_nfs_info: called with host <...> proto 6 version 0x40
  automount[115692]: get_portmap_client: error 0x3 getting portmap client
  automount[115692]: mount(nfs): no hosts available

  I think it is the same bug reported on the autofs mailing list here:
  https://www.spinics.net/lists/autofs/msg02389.html
  Apparently, it has been introduced in the transition of autofs from 5.1.7 to 5.1.8.

  A fix has been posted here:
  https://www.spinics.net/lists/autofs/msg02391.html

  It would be great if this fix could be included in Ubuntu 22.04, such
  that I can update my clients. As my setup should not be too exotic, I
  guess there are other people who will face the same problem when they
  are doing the Ubuntu update to the new LTS version.

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