[Bug 1970264] Re: autofs fails to mount nfs4 shares

[Michael Kiermaier]

Maybe this one
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1965643
is the same bug. It is hard to tell as not much info is given.

** Description changed:

- I'm running a server which provides NFSv4 shares. The clients mount
- these shares via automount + LDAP.
+ 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 automount mechanism to work.
+ 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 automount mechanism to work any more.
  After the update, the autofs package version is 5.1.8-1ubuntu1.
  
  Setting autofs to verbose mode, the crucial lines in /var/log/syslog on the client are
  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.
- Otherwise, I cannot update my clients. As my setup is not 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.
+ Otherwise, I cannot 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.

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

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 automount mechanism to work any more.
  After the update, the autofs package version is 5.1.8-1ubuntu1.

  Setting autofs to verbose mode, the crucial lines in /var/log/syslog on the client are
  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.
  Otherwise, I cannot 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