On Mon, Dec 31, 2018 at 12:31:11PM -0800, Sunil Mohan Adapa wrote: > On Tue, 27 Nov 2018 14:29:40 -0500 Eric Garver <e...@garver.life> wrote: > [...] > > That makes it smell like an iptables-restore issue in the nftables > > backed version of iptables. It would be great if we could reproduce > > without firewalld using iptables-restore. > > A much simpler way I reproduced the problem with iptables-restore: > > # iptables-restore <<END > *security > :INPUT_direct - [0:0] > -A INPUT -j INPUT_direct > COMMIT > END > > # sleep 1 > > # iptables-restore -n <<END > *security > -F > -X > -Z > COMMIT > END > iptables-restore v1.8.2 (nf_tables): > line 4: RULE_REPLACE failed (No such file or directory): rule in chain INPUT
Thanks Sunil! I confirmed on my end. I also filed a report against RHEL. https://bugzilla.redhat.com/show_bug.cgi?id=1664829