Bug 1912877

Summary: nfs: Unknown parameter 'defaultvers'
Product: [Fedora] Fedora Reporter: Derrien <derrien>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: bfields, imc, steved, yoyang
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nfs-utils-2.5.2-1.rc4.fc33 nfs-utils-2.5.2-1.rc4.fc32 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-01-10 01:27:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Derrien 2021-01-05 13:42:14 UTC
Description of problem:
With Defaultvers= actived in /etc/nfsmount.conf we get 

Jan  5 11:09:51 t5820 kernel: nfs: Unknown parameter 'defaultvers'

and automount doesn't work anymore

Version-Release number of selected component (if applicable):
nfs-utils-2.5.2-1.rc3

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ian Collier 2021-01-07 12:22:52 UTC
This is a regression from rc1.  I assume it is accidental because 'Defaultvers'
is still mentioned in the sample nfsmount.conf in rc3.

This commit: http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=88c22f924f1b71c1efd13945f05f5cbfa370acc4
says that default options are left on the options list and then all
"defaultfoo" options are removed at the end.  But it seems to me that this:

        /*
         * Strip out defaults, which have already been handled,
         * then join the rest and return.
         */
        po_remove_all(options, "default");

doesn't actually work.  I could be wrong as I don't properly understand
the code.

Comment 2 Steve Dickson 2021-01-07 15:53:23 UTC
Here is the proposed upstream patch 

https://www.spinics.net/lists/linux-nfs/msg81516.html

Comment 3 Fedora Update System 2021-01-08 16:26:43 UTC
FEDORA-2021-3029fca4c2 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-3029fca4c2

Comment 4 Fedora Update System 2021-01-09 01:13:06 UTC
FEDORA-2021-2f77ff1189 has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-2f77ff1189`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-2f77ff1189

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2021-01-09 01:20:49 UTC
FEDORA-2021-3029fca4c2 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-3029fca4c2`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-3029fca4c2

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2021-01-10 01:27:36 UTC
FEDORA-2021-3029fca4c2 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2021-01-24 01:21:46 UTC
FEDORA-2021-2f77ff1189 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.