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.
Bug 1551903 - nfsdcltrack fails to initialize the database in arches other than x86_64
Summary: nfsdcltrack fails to initialize the database in arches other than x86_64
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nfs-utils
Version: 7.5
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Yongcheng Yang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-06 07:00 UTC by Yongcheng Yang
Modified: 2018-10-30 11:48 UTC (History)
1 user (show)

Fixed In Version: nfs-utils-1.3.0-0.56.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 11:48:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3311 0 None None None 2018-10-30 11:48:44 UTC

Description Yongcheng Yang 2018-03-06 07:00:58 UTC 
Description of problem:
"nfsdcltrack init" fails in arches ppc64, ppc64le, aarch64 or s390x (except x86_64).

Previously It returned "0" and we just didn't notice it until Bug 1461349 was fixed.

However, I have no idea whether it's expected or not. Do we support nfsdcltrack in those arches?


Version-Release number of selected component (if applicable):
This has been existing for long time and still reproducible in nfs-utils-1.3.0-0.54.el7


How reproducible:
100% easy

Steps to Reproduce:
1. nfsdcltrack init

Actual results:
[root@~]# rpm -q nfs-utils
nfs-utils-1.3.0-0.50.el7.ppc64
[root@~]# systemctl restart nfs
[root@~]# nfsdcltrack init
Usage: nfsdcltrack [ -hfd ] [ -s dir ] < cmd > < arg >
Where < cmd > is one of the following and takes the following < arg >:
    init
    create <nfs_client_id4>
    remove <nfs_client_id4>
    check  <nfs_client_id4>
    gracedone <epoch time>
[root@~]# echo $?
0
^^^
[root@~]# rpm -Uvh nfs-utils-1.3.0-0.51.el7.ppc64.rpm >/dev/null
[root@~]# rpm -q nfs-utils
nfs-utils-1.3.0-0.51.el7.ppc64
[root@~]# systemctl restart nfs
[root@~]# nfsdcltrack init
Usage: nfsdcltrack [ -hfd ] [ -s dir ] < cmd > < arg >
Where < cmd > is one of the following and takes the following < arg >:
    init
    create <nfs_client_id4>
    remove <nfs_client_id4>
    check  <nfs_client_id4>
    gracedone <epoch time>
[root@~]# echo $?
1
^^
[root@~]#


Expected results:
success
Comment 1 Steve Dickson 2018-06-25 17:23:31 UTC 
commit a1f4e16d0426274d15c785ead3584bb7f9df32fd
Author: Steve Dickson <steved>
Date:   Sun Jun 24 14:21:24 2018 -0400

    nfsdcltrack: getopt_long() fails on a non x86_64 archs
Comment 5 errata-xmlrpc 2018-10-30 11:48:04 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.