Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Configured the "/etc/sysconfig/nfs" to not permitting NFSv4.1 or NFSv4.2, then restore them all. It turns out that NFS minor version 4.1 and 4.2 are continued to be disabled.
Version-Release number of selected component (if applicable):
nfs-utils-1.3.0-0.33.el7
How reproducible:
100% easy
Steps to Reproduce:
1. echo "RPCNFSDARGS=\"-N 4.1 -N 4.2\"" > /etc/sysconfig/nfs
2. systemctl restart nfs
3. echo "" > /etc/sysconfig/nfs
4. systemctl restart nfs
5. cat /proc/fs/nfsd/versions | grep '+4.1 +4.2'
Actual results:
-------------------------------------------------------------
# systemctl start nfs
# cat /proc/fs/nfsd/versions
-2 +3 +4 +4.1 +4.2
# echo "RPCNFSDARGS=\"-N 4.1 -N 4.2\"" > /etc/sysconfig/nfs
# systemctl restart nfs
# cat /proc/fs/nfsd/versions
-2 +3 +4 -4.1 -4.2 <<<<<<<<<<< 4.1/4.2 disabled as expected
# > /etc/sysconfig/nfs
# systemctl restart nfs
# cat /proc/fs/nfsd/versions
-2 +3 +4 -4.1 -4.2 <<<<<<<<<<< cannot turn on them then
#
Expected results:
Turn on the default NFS (minor) version as default. Even someone used to disable them before.
Additional info:
1. Specifying major NFS version ("-N 3" or "-N 4") doesn't have this problem;
2. Can reproduce this issue even with latest upstream nfs-utils version.
Method to work around:
Request that certain NFS minor versions using "-V" after that.
-------------------------------------------------------------
# cat /etc/sysconfig/nfs
# systemctl restart nfs
# cat /proc/fs/nfsd/versions
-2 +3 +4 -4.1 -4.2
# echo "RPCNFSDARGS=\"-V 4.1 -V 4.2\"" > /etc/sysconfig/nfs
# cat /etc/sysconfig/nfs
RPCNFSDARGS="-V 4.1 -V 4.2" <<<<<<<<<<<<<<<< to workaround it
# systemctl restart nfs
# cat /proc/fs/nfsd/versions
-2 +3 +4 +4.1 +4.2
# > /etc/sysconfig/nfs
# cat /etc/sysconfig/nfs
# systemctl restart nfs
# cat /proc/fs/nfsd/versions
-2 +3 +4 +4.1 +4.2
#
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:3311
Description of problem: Configured the "/etc/sysconfig/nfs" to not permitting NFSv4.1 or NFSv4.2, then restore them all. It turns out that NFS minor version 4.1 and 4.2 are continued to be disabled. Version-Release number of selected component (if applicable): nfs-utils-1.3.0-0.33.el7 How reproducible: 100% easy Steps to Reproduce: 1. echo "RPCNFSDARGS=\"-N 4.1 -N 4.2\"" > /etc/sysconfig/nfs 2. systemctl restart nfs 3. echo "" > /etc/sysconfig/nfs 4. systemctl restart nfs 5. cat /proc/fs/nfsd/versions | grep '+4.1 +4.2' Actual results: ------------------------------------------------------------- # systemctl start nfs # cat /proc/fs/nfsd/versions -2 +3 +4 +4.1 +4.2 # echo "RPCNFSDARGS=\"-N 4.1 -N 4.2\"" > /etc/sysconfig/nfs # systemctl restart nfs # cat /proc/fs/nfsd/versions -2 +3 +4 -4.1 -4.2 <<<<<<<<<<< 4.1/4.2 disabled as expected # > /etc/sysconfig/nfs # systemctl restart nfs # cat /proc/fs/nfsd/versions -2 +3 +4 -4.1 -4.2 <<<<<<<<<<< cannot turn on them then # Expected results: Turn on the default NFS (minor) version as default. Even someone used to disable them before. Additional info: 1. Specifying major NFS version ("-N 3" or "-N 4") doesn't have this problem; 2. Can reproduce this issue even with latest upstream nfs-utils version. Method to work around: Request that certain NFS minor versions using "-V" after that. ------------------------------------------------------------- # cat /etc/sysconfig/nfs # systemctl restart nfs # cat /proc/fs/nfsd/versions -2 +3 +4 -4.1 -4.2 # echo "RPCNFSDARGS=\"-V 4.1 -V 4.2\"" > /etc/sysconfig/nfs # cat /etc/sysconfig/nfs RPCNFSDARGS="-V 4.1 -V 4.2" <<<<<<<<<<<<<<<< to workaround it # systemctl restart nfs # cat /proc/fs/nfsd/versions -2 +3 +4 +4.1 +4.2 # > /etc/sysconfig/nfs # cat /etc/sysconfig/nfs # systemctl restart nfs # cat /proc/fs/nfsd/versions -2 +3 +4 +4.1 +4.2 #