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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970264
Title:
autofs fails to mount nfs4 shares with "error 0x3 getting portmap
client"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1970264/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
