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.
The update of the nfs-utils packages in Red Hat Enterprise Linux 7.2 added support for the NFSv4.1 features which was incomplete. Consequently, the NFSv4 client-tracking callout program (nfsdcltrack) created an incorrect schema for the clients table, and the file locks appeared then but these locks did not persist after restart. With this update, the underlying source code has been fixed, and nfsdcltrack can now enter the NFS client data into the database. As a result, NFS clients no longer experience the incorrect locks after NFS server restart.
I've done the commit
commit e3cd958a42458fdb5fdd24d15b052ca4d034965c
Author: Steve Dickson <steved>
Date: Mon Feb 22 16:58:21 2016 -0500
Update to nfsdcltrack v2 schema (bz 1309625)
Signed-off-by: Steve Dickson <steved>
Resolves: bz1309625
But the NVR does not increase from _2 to _3
so the build fails with:
rhpkg build
Could not execute build: Package nfs-utils-1.3.0-0.21.el7_2 has already been built
Note: You can skip this check with --skip-nvr-check. See help for more info.
make: *** [build] Error 1
I'm a bit confused. This bug is marked "Fixed In Version: nfs-utils-1.3.0-0.21.el7_2" but advisory RHBA-2016:0206-1does not mention that it includes the fix for this issue. Is it fixed in nfs-utils-1.3.0-0.21.el7_2 or not? If not, why is this bug marked that it is?
(In reply to Steve Dickson from comment #6)
> I've done the commit
> commit e3cd958a42458fdb5fdd24d15b052ca4d034965c
> Author: Steve Dickson <steved>
> Date: Mon Feb 22 16:58:21 2016 -0500
>
> Update to nfsdcltrack v2 schema (bz 1309625)
>
> Signed-off-by: Steve Dickson <steved>
> Resolves: bz1309625
>
> But the NVR does not increase from _2 to _3
> so the build fails with:
>
> rhpkg build
> Could not execute build: Package nfs-utils-1.3.0-0.21.el7_2 has already been
> built
> Note: You can skip this check with --skip-nvr-check. See help for more info.
> make: *** [build] Error 1
As in bug #1325769, I suspect that the Release in the spec file needs to be incremented. Could that be the problem, Steve? Thanks!
(In reply to Steve Dickson from comment #9)
> Again, how do I update the Release: to make this happen?
I _think_ it should be:
Release: 0.22%{?dist}
Or anything that fits your versioning scheme. Does it make sense this way?
(In reply to Marcel Kolaja from comment #10)
> (In reply to Steve Dickson from comment #9)
> > Again, how do I update the Release: to make this happen?
>
> I _think_ it should be:
>
> Release: 0.22%{?dist}
>
> Or anything that fits your versioning scheme. Does it make sense this way?
As I said in the othr bz... the original released NVR has to be persevere
THe _# is Z-stream version.
(In reply to Steve Dickson from comment #11)
> (In reply to Marcel Kolaja from comment #10)
> > (In reply to Steve Dickson from comment #9)
> > > Again, how do I update the Release: to make this happen?
> >
> > I _think_ it should be:
> >
> > Release: 0.22%{?dist}
> >
> > Or anything that fits your versioning scheme. Does it make sense this way?
>
> As I said in the othr bz... the original released NVR has to be persevere
> THe _# is Z-stream version.
Similarly as in the other bug, yes, it's shouldn't be 0.22%{?dist}. Sorry for that. Does this work?
Release: 0.21%{?dist}.1
This is not fixed... I'm still getting the error with nfs-utils-1.3.0-0.21.el7_2:
May 10 10:44:51 nfs4-server nfsdcltrack[29235]: sqlite_insert_client: insert statement prepare failed: table clients has 2 columns but 3 values were supplied
I'm also wondering if it's related to an ABRT crash report I've recently received. I'll post the report as an attachment.
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-2016:1258