Bug 1806642

Summary: Disable libiptc in keepalived
Product: Red Hat Enterprise Linux 8 Reporter: Ryan O'Hara <rohara>
Component: keepalivedAssignee: Ryan O'Hara <rohara>
Status: CLOSED ERRATA QA Contact: Brandon Perkins <bperkins>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.2CC: cfeist, cluster-maint
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: keepalived-2.0.10-10.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:05:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ryan O'Hara 2020-02-24 16:44:47 UTC 
Keepalived has the option to build with iptables and/or nftables support. In RHEL8, keepalived is being built with iptables support where rules were created via calls to libiptc. These would be iptables "legacy" rules. Attempting to view said rules (iptables -L) would cause a warning:

# Warning: iptables-legacy tables present, use iptables-legacy to see them

However, RHEL8 does not provide iptables-legacy.

The solution is to disable libiptc at build time for keepalived in RHEL8. Also remove the BuildRequires for iptables-devel and ipset-devel, to be replaced with libmnl-devel and libnftnl-devel (for nftables support).

The result should be:

1. If 'nftables' is used in the config file, nftables tables/rules will be created via library calls.

2. If 'vrrp_iptables' is used in the config file, iptables will be called via a system() call. Since iptables in RHEL8 is 'iptables-nft' (not 'iptables-legacy'), this will also work.

Note that disabling libiptc will also disable ipset support at build time.
Comment 7 errata-xmlrpc 2020-04-28 16:05:02 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-2020:1753