'python-iptables: match "state" already registered' on AWS Linux about agent HOT 5 CLOSED

This also impacts the upgrade feature:

[ec2-user@wott-aws-linux-1 ~]$ sudo wott-agent upgrade qemu-guest-agent
wott-agent version wott-agent 0.1.5.800
upgrade packages: ['qemu-guest-agent']
The following packages will be upgraded:

Confirm: [y/N]y
python-iptables: match "state" already registered
[ec2-user@wott-aws-linux-1 ~]$

from agent.

This appears to affect Debian too:

mvip@wott-debian-buster:~$ sudo wott-agent upgrade libicu63

wott-agent version wott-agent 0.1.5.801-6c71abb
upgrade packages: ['libicu63']
Hit http://security.debian.org/debian-security buster/updates InRelease
Hit http://deb.debian.org/debian buster InRelease
Hit http://deb.debian.org/debian buster-updates InRelease
Hit https://packagecloud.io/wott/agent/debian buster InRelease
Fetched 0 B in 0s (0 B/s)
The following packages will be upgraded:

Confirm: [y/N]python-iptables: match "state" already registered
mvip@wott-debian-buster:~$

from agent.

ldx/python-iptables#282
From what I understood, the new version of iptables has this incompatibility with the python3-iptables (0.13) which is unfortunately not being updated in newer Debians.

we can try the hacks and workarounds given there. Or think of smth else.

from agent.

The commit chruss2/python-iptables@282c790 which fixes the crash is not in
Debian Upstream yet. For Debian/Ubuntu we have the following options:

1. build the newest python-iptables deb from source using fpm (the same way we build for Amazon Linux)
2. build the newest python-iptables deb from source using Debian build scripts
3. merge chruss2/python-iptables@282c790 into 0.13.0-2 or 0.14.0_ds-1 (whichever is possible) and build a deb from there.

I would prefer 3. because this way we most probably avoid breaking other components which use python-iptables. But If it turns out impossible then try 2. 1. is a fallback.

On Amazon Linux it should be enough to just build the rpm from Github source, not from pip, which is also obsolete.

All of this will work provided that the fixing commit does the job, of course.

from agent.

Since the fix is already in python-iptables upstream repo, we can expect it to be released with the next version of the package. So, as a temporary solution it's enough to monkey-patch a couple of methods with this bug. See my PR: #289

from agent.