** Tags removed: server-todo verification-needed
--
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
This bug was fixed in the package autofs - 5.1.8-1ubuntu1.1
---
autofs (5.1.8-1ubuntu1.1) jammy; urgency=medium
* d/p/fix-nfsv4-only-mounts-should-not-use-rpcbind.patch:
Make NFSv4-only mounts not depend on rpcbind. (LP: #1970264)
-- Sergio Durigan Junior Thu, 28 Apr
2022
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
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
On Wednesday, May 04 2022, Michael Kiermaier wrote:
> Thanks you for the detailed response.
>
> I have to say that this was the first time that I was confronted with
> the 'proposed'-repository. I followed the instructions at
> https://wiki.ubuntu.com/Testing/EnableProposed without too much
>
Thanks you for the detailed response.
I have to say that this was the first time that I was confronted with
the 'proposed'-repository. I followed the instructions at
https://wiki.ubuntu.com/Testing/EnableProposed without too much
investigation of the precise effect of the single steps.
Thereby,
On Wednesday, May 04 2022, Michael Kiermaier wrote:
> @Brian Murray
> In the process, I see the following:
>
> apt-get install autofs/jammy-proposed
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Selected version '5.1.8-1ubuntu1.1'
I can confirm that the package autofs-5.1.8-1ubuntu1.1 solves the
original problem, as long as it is a "pure" automount without LDAP
involved.
It is clear that a LDAP-based automount cannot work as the autofs-ldap
package has been uninstalled.
--
You received this bug notification because you
@Brian Murray
In the process, I see the following:
apt-get install autofs/jammy-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '5.1.8-1ubuntu1.1' (Ubuntu:22.04/jammy-proposed [amd64]) for
'autofs'
The following packages
Hello Michael, or anyone else affected,
Accepted autofs into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/autofs/5.1.8-1ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package autofs - 5.1.8-1ubuntu2
---
autofs (5.1.8-1ubuntu2) kinetic; urgency=medium
* d/p/fix-nfsv4-only-mounts-should-not-use-rpcbind.patch:
Make NFSv4-only mounts not depend on rpcbind. (LP: #1970264)
-- Sergio Durigan Junior Thu, 28 Apr
2022
** Description changed:
[ Impact ]
NFSv4-only shares cannot be automounted if the server isn't running (or
is blocking) rpcbind, even though NFSv4 doesn't require rpcbind anymore.
[ Test Plan ]
You will two Jammy VMs (unfortunately lxd VMs won't work, so you will
likely need
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/autofs/+git/autofs/+merge/420903
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/autofs/+git/autofs/+merge/420904
--
You received this bug notification because you are a member of
** Description changed:
+ [ Impact ]
+
+ NFSv4-only shares cannot be automounted if the server isn't running (or
+ is blocking) rpcbind, even though NFSv4 doesn't require rpcbind anymore.
+
+ [ Test Plan ]
+
+ You will two Jammy VMs (unfortunately lxd VMs won't work, so you will
+ likely need
These are good news, thank you so much!
--
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
Thanks for the further info, Michael.
I was able to reproduce the problem here. The trick was to mount the
share from another VM. I was able to backport the upstream patch, build
autofs with it and verify that it indeed fixes the problem.
Unfortunately, it seems that upstream hasn't pushed the
Here is some more info:
The server runs with an enabled UFW firewall. It was set up via
ufw allow from to any port nfs proto tcp
Here is the server output of 'ufw status'
Status: active
To Action From
-- --
OpenSSH
Many thanks for looking into this.
I guess a "quick reproducer" means that I have to set up 2 fresh 22.04
installs, and then do a minimal configuration of one as a server
(provide NFSv4 share) and on the other install as a client (pull in
NFSv4 share via autofs mount). This would take some time.
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
** Description changed:
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
** Description changed:
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
** Description changed:
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
** Summary changed:
- autofs fails to mount nfs4 shares
+ autofs fails to mount nfs4 shares with "error 0x3 getting portmap client"
--
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:
22 matches
Mail list logo
