Red Hat Bugzilla – Bug 1477572
Keepalived 1.3.x ipset functionality seems to be broken
Last modified: 2018-04-10 14:15:57 EDT
Description of problem: After updating from RHEL 7.3 to 7.4 (thus keepalived 1.2.x -> 1.3.x), the logs spew this: Aug 2 14:00:01 tux1 Keepalived_vrrp[6935]: Unable to load ipset library - libipset.so.3: cannot open shared object file: No such file or directory Strange. I never configured ipset before. And ipset is also not a dependency of the keepalived package. Documentation, specifically "man keepalived.conf" says: # Keepalived may have the option to use ipsets in conjunction with iptables. # If so, then the ipset names can be specified, defaults as below. # If no names are specified, ipsets will not be used, otherwise any omitted # names will be constructed by adding "_if" and/or "6" to previously specified # names. vrrp_ipset [keepalived [keepalived6 [keepalived_if6]]] From my understanding, just putting "vrrp_ipset" into global_defs section should do the trick, right? Logs look then like this: Aug 2 14:02:36 tux1 Keepalived_vrrp[7145]: Unknown keyword 'vrrp_ipset' Aug 2 14:02:36 tux1 Keepalived_vrrp[7145]: Unable to load ipset library - libipset.so.3: cannot open shared object file: No such file or directory Hum? It feels like the keepalived 1.3.x ipset functionality seems to be broken in general. And if I install ipset using "yum install ipset", this is still strange after a restart: Aug 2 14:04:44 tux1 Keepalived_healthcheckers[7184]: Unknown keyword 'vrrp_ipset' Aug 2 14:04:44 tux1 Keepalived_vrrp[7185]: Unknown keyword 'vrrp_ipset' Aug 2 14:04:44 tux1 kernel: ip_set: protocol 6 The configuration option as mentioned in the documentation does still not exist/work, but now I even have ipset enabled (not desired in this case). Version-Release number of selected component (if applicable): keepalived-1.3.5-1.el7.x86_64 How reproducible: Everytime, see above. Actual results: Keepalived yells for missing "libipset.so.3" and "vrrp_ipset" has no effect. Expected results: Working options to disable ipset functionality.
Cross-filed ticket 01903060 on the Red Hat customer portal.
Please install 'ipset-libs' while we determine what dependency is missing from the rpm.
As already mentioned above, this does not make things better. Installing ipset just enables ipset support unconditionally, which I do not want to have enabled (according to the docs, "vrrp_ipset" should disable ipset; keepalived itself is also up and running when having the ipset package not installed - the issue here is that keepalived does not handle ipset dependency and vrrp_ipset keyword properly).
Or simpler said: Even "vrrp_ipset" keyword usage (= disable) according to the documentation and the missing "libipset.so.3" errors show up in the logs, keepalived works - and indeed without ipset support. But this behaviour feels just broken.
(In reply to Ryan O'Hara from comment #3) > Please install 'ipset-libs' while we determine what dependency is missing > from the rpm. OK, so 'ipset-libs' was pulled in when you installed 'ipset'. We need to fix the spec file to that keepalived has a dependency on 'ipset-libs'. The other bug here is in the man page. The keyword should be "vrrp_ipsets", not "vrrp_ipset". I reported this upstream this morning and it is already fixed. We will also need to fix the man page in RHEL.
Thanks! :) But are you sure that disabling using "vrrp_ipsets" works? global_defs { # … vrrp_ipsets } leads to: Aug 2 22:12:40 tux1 kernel: Netfilter messages via NETLINK v0.30. Aug 2 22:12:40 tux1 kernel: ip_set: protocol 6 Why does keepalived load ipset, even I disable it using the setting?
(In reply to Robert Scheck from comment #7) > Why does keepalived load ipset, even I disable it using the setting? In my experience, specifying "vrrp_ipsets" in the global_defs will enable ipsets. The upstream documentation is a bit confusing because it says that not specifying a name will disable ipsets, but it also says that the there is a default ipset4 name (keepalived). That is from the keepalived.conf.SYNOPSIS. On the other name, the keepalived.conf man page says otherwise. If you don't want ipsets, I'd just not specify in the config.
I dislike the difference between experience and documentation here. Let us please clarify this with upstream if needed and if the documentation is not correct, let us correct the documentation. As of writing, the documentation shipped with keepalived (man page) says, just "vrrp_ipsets" should disable it (from keepalived man page: "If no names are specified, ipsets will not be used, otherwise any omitted"), however it obviously loads some ipset related kernel stuff.
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-2018:0972