nfs-utils-1.3.0-0.21.el7_2 already exists... so I really don't know what to do to get this in the errata...

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!

Again, how do I update the Release: to make this happen?

(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.

Created attachment 1155774 [details]
Crash report

I don't know if this is related to this issue...

Move to VERIFIED according to comment 16

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