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.
Ah this, I had noticed something similar before, it comes down to a fundamental flaw in pythons getopt handling, it cannot cope with optional arguments, deliberately. I will see what can be done to work around this issue.
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-2020:1832
Description of problem: The rpc.nfsd can accept both args "--rdma" (same as -r) and "--rdma=port". But in rhel8, current nfsconvert.py seemingly require an extra port_number when dealing with "--rdma": ~~~~~~~~ [yoyang@ nfs-utils.rhel8]$ grep rdma nfsconvert.py LONG_NFSD = ['debug', 'host=', 'port=', 'rdma=', 'nfs-version=', 'no-nfs-version=', '-r': (CONF_NFS, 'nfsd', 'rdma', 'nfsrdma'), '-R': (CONF_NFS, 'nfsd', 'rdma', '$1'), '--rdma': (CONF_NFS, 'nfsd', 'rdma', '$1'), <<<< ~~~~~~~~ And then fail to convert the previous /etc/sysconfig/nfs setting of RPCNFSDARGS="--rdma" Btw, there's another rhel8 rdma issue bz1710532 about nfs.conf rdma seetings. And IMHO we'd better to update the rdma config splitting into 2 lines, e.g. # rdma=yes # rdma-port=20049 Version-Release number of selected component (if applicable): nfs-utils-2.3.3-25.el8 How reproducible: always easy Steps to Reproduce: 1. echo 'RPCNFSDARGS="--rdma"' > /etc/sysconfig/nfs 2. systemctl restart nfs-server Actual results: [root.0 ~]# vi /etc/sysconfig/nfs [root.0 ~]# >/etc/nfs.conf [root.0 ~]# cat /etc/sysconfig/nfs RPCNFSDARGS="--rdma" [root.0 ~]# systemctl restart nfs-server A dependency job for nfs-server.service failed. See 'journalctl -xe' for details. [root.0 ~]# cat /etc/nfs.conf [root.0 ~]# [root.0 ~]# rpm -q nfs-utils nfs-utils-2.3.3-24.el8.x86_64 [root.0 ~]# Success results when using "--rdma=port": [root.0 ~]# cat /etc/sysconfig/nfs RPCNFSDARGS="--rdma=12334" [root.0 ~]# systemctl restart nfs-server [root.0 ~]# cat /etc/nfs.conf [nfsd] rdma = 12334 [root.0 ~]# Additional info: # rhel7 can consume the setting: [root~]# vi /etc/sysconfig/nfs [root~]# cat /etc/sysconfig/nfs RPCNFSDARGS="--rdma" [root~]# systemctl restart nfs-server [root~]# cat /proc/fs/nfsd/portlist | grep -w rdma rdma 20049 rdma 20049 [root~]# rpm -q nfs-utils nfs-utils-1.3.0-0.65.el7.x86_64 [root~]#