ipt_CLUSTERIP is deprecated and it will removed soon, use xt_cluster instead
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
resource-agents (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
pacemaker still uses iptable's "CLUSTERIP" -- and dmesg shows a deprecation warning:
[ 15.027333] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
[ 15.027464] ipt_CLUSTERIP: ipt_CLUSTERIP is deprecated and it will removed soon, use xt_cluster instead
~# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
CLUSTERIP all -- anywhere proxy.charite.de CLUSTERIP hashmode=
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pacemaker 1.1.14-2ubuntu1.1
ProcVersionSign
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Sep 23 17:26:01 2016
InstallationDate: Installed on 2014-08-19 (766 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3)
SourcePackage: pacemaker
UpgradeStatus: Upgraded to xenial on 2016-09-22 (1 days ago)
tags: | added: ubuntu-ha |
Hi,
I tried to recreate the issue by adding a clusterip like in the examples:
pcs resource create ClusterIP IPaddr2 ip=192.168.0.120 cidr_netmask=32
But at least for me that didn't trigger anything.
I might just not have a complete enough configuration to show the issue. I guess I need to config further and start what I defined. It would be nice if you could share whatever you consider required to reproduce.
Looking at the sources I don't see that Ubuntu does anything special to add or select clusterip.
So my assumption would be that this is an upstream bug, but I'd like to see a bit more of what you can share to reproduce before finally deciding on that.