Description of problem:
Condition for NETWORK_LACP_BOND_LACPDU_ISSUE rule is triggered by a kernel version that is also fixed. The condition uses a later kernel version (kernel-3.10.0-1062.el7). But the fix is also available in kernel-3.10.0-957.35.1.el7.

[ bonding/802.3ad: fix slave link initialization transition states ]
( https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=334031219a84b9994594015aab85ed7754c80176 )

Referencing rule proposal: https://projects.engineering.redhat.com/browse/CEECBA-2600

KB mentions correct kernel version in Resolution table for RHEL 7.6-EUS.
But condition doesn't include this kernel version.
https://access.redhat.com/solutions/4122011

Customer can not use the kernel-3.10.0-1062.el7 version because the live kernel patching enhancement is not applicable to the Customer's patching processes.

Version-Release number of selected component (if applicable):
RHEL 7.6
kernel-3.10.0-957.35.1.el7

How reproducible:
Only update to kernel-3.10.0-957.35.1.el7 and not the later kernel-3.10.0-1062.el7

Steps to Reproduce:
1. Don't apply the live kernel patching enhancement (RHEA-2019:2011 and onward)
2. Only update to kernel-3.10.0-957.35.1.el7

Actual results:
Fixed kernel-3.10.0-957.35.1.el7 is triggering the rule.

Expected results:
Fixed kernel version shouldn't trigger rule.

Additional info:
RHEL 7.6 EUS still has about 3 more years of support.