Your message dated Wed, 31 Jul 2019 14:32:46 +0300
with message-id <[email protected]>
and subject line Fixed in version 1.8.3
has caused the Debian Bug report #931722,
regarding Firewalld fails when startig and when reloading rules
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
931722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931722
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: firewalld
Version: 0.6.3-5

When one runs firewall-cmd --reload, and when firewalld starts, the
following error appears


2019-07-09 17:02:15 ERROR: '/usr/sbin/iptables-restore -w -n' failed:
iptables-restore v1.8.2 (nf_tables):
line 4: RULE_REPLACE failed (No such file or directory): rule in chain INPUT
line 4: RULE_REPLACE failed (No such file or directory): rule in chain OUTPUT


Fix:

The cause of the bug is that iptables restore fails when both -F and
-Z are applied in the same table (see
https://bugzilla.redhat.com/show_bug.cgi?id=1664829 )

In file /usr/lib/python3/dist-packages/firewall/core/ipXtables.py
remove the flag -Z


--- /usr/lib/python3/dist-packages/firewall/core/ipXtables.py.orig
 2019-07-09 17:37:33.915510550 +0200
+++ /usr/lib/python3/dist-packages/firewall/core/ipXtables.py
2019-07-09 17:02:09.251902978 +0200
@@ -551,7 +551,8 @@
             # Flush firewall rules: -F
             # Delete firewall chains: -X
             # Set counter to zero: -Z
-            for flag in [ "-F", "-X", "-Z" ]:
+            #for flag in [ "-F", "-X", "-Z" ]:
+            for flag in [ "-F", "-X"  ]:
                 rules.append(["-t", table, flag])
         return rules

--- End Message ---
--- Begin Message ---
Version: 1.8.3-2

This bug has been fixed upstream in version 1.8.3.

-- 
Arto Jantunen

--- End Message ---

Reply via email to