Look like a potential patchset to backport without having to bump
version in stable release:
6e2e169eb iptables: remove duplicated argument parsing code
24f81746 xshared: do not lock again and again if "-w" option is not specified
72bb3dbf0 xshared: using the blocking file lock request when we wait
indefinitely
999eaa24 iptables-restore: support acquiring the lock.
65801d02 iptables-restore.8: document -w/-W options
21ba5b38 ip{,6}tables-restore: Don't accept wait-interval without wait
I'll test it, and then will talk w/ the SRU verification team to see if
eligible for SRU.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1791958
Title:
iptables-restore is missing -w option
Status in iptables package in Ubuntu:
Confirmed
Bug description:
For CRIU we need to have iptables version 1.6.2 which includes the
'-w' option in iptables-restore.
This is a request to update iptables to 1.6.2 in 18.10 and if possible
backport the necessary changes to 18.04.
The CRIU project gets right now many bug reports (mostly in the
combination LXD + CRIU) due to the missing '-w' option in iptables-
restore. Especially as 18.04 will be around for some time it would be
good to have iptables-restore available with '-w'.
This is one example bug report: https://github.com/checkpoint-
restore/criu/issues/551
But not only CRIU would benefit from this change. It seems also
problematic with Kubernetes:
https://github.com/kubernetes/kubernetes/pull/60978
So if possible, please update iptables to 1.6.2 (or backport changes)
to support -w in iptables-restore.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1791958/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
