This bug was fixed in the package nfs-utils - 1:1.3.4-2.5ubuntu3.6
---------------
nfs-utils (1:1.3.4-2.5ubuntu3.6) focal; urgency=medium
* Fix default protocol version negotiation when NFSv4 is specified
on the command line with '-t nfs4' or '-o vers=4', such that it
actually follows the previously agreed-upon laddering approach,
of trying 4.2, then 4.1, then 4.0 before raising an error.
These patches also fix an issue where asking for a v4 mount could
result in a v3 mount if the namespace was available in v3, but
not in v4, such as with fsid=0. (LP: #2049262)
- d/p/lp-2049262-1-mount.nfs-improve-version-negotiation-when-vers-4-i.patch
- d/p/lp-2049262-2-mount.nfs-Use-default-minor-version-when-t-nfs4-is.patch
- d/p/lp-2049262-3-mount.nfs-Use-default-minor-version-when-o-v4-is-sp.patch
-- Matthew Ruffell <[email protected]> Thu, 18 Jan 2024
22:29:59 +1300
** Changed in: nfs-utils (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049262
Title:
mount.nfs: fix version negotiation laddering with parameters '-t nfs4'
or '-o vers=4'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2049262/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
