This bug has been copied from bug #1477413 and has been proposed to be backported to 7.4 z-stream (EUS).
I don't think -17 is affected. We currently experience failures for OpenStack Neutron with -18 with a similar issue; with -17, it passes broken tests just fine.
By the quick look at backported iptables patches, it doesn't seem like xlock was a thing in -17 at all, so you can't possibly get the error there.
This is affecting Red Hat OpenStack CI, can we have the latest status here?
I'm putting this back ON_QA. There is a new bug 1486871 to track the issue found in comment 6.
*** Bug 1460116 has been marked as a duplicate of this bug. ***
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.
Obviously, the QA for this update was incomplete, leading to bug #1499367 now.