Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
$subject

Version-Release number of selected component (if applicable):
firewalld-0.3.9-7.el7.noarch

How reproducible:
sometimes

Steps to Reproduce:
Not really sure tough. I had firewalld disabled because I was doing some debugging hence didn't want firewalld interfering. After reboot 'firewall-cmd --state' prints out that firewalld is not running, but after consulting output of systemctl I can see firewalld daemon process is running.

Actual results:
firewalld is running as per output of 'systemctl status firewalld.service' but 'firewall-cmd --state' reports "not-running".

Expected results:
firewalld is running as per output of 'systemctl status firewalld.service' and 'firewall-cmd --state' reports "running".

Additional info:
/var/log/firewalld attached

Created attachment 945329 [details]
firewalld debug log

Something seems to be using iptables command at the same moment as firewalld.

I tried:

while true;
do
  lsof -U | grep xtables
done

to catch the culprit with no luck (but I guess it's libvirtd).

We might use a patch [1] for iptables and then add for example -w2 to each iptables call in firewalld. I tried that some time ago and it worked nicely (I actually created that patch for this reason).

[1] https://git.netfilter.org/iptables/commit/?id=aaa4ace72ba1d195bbf436134a336816c33f7bd0

(In reply to Jiri Popelka from comment #3)
> I tried:

Some time ago when I was also seeing this.

(In reply to Jiri Popelka from comment #3)
> ... add for example -w2 to each
> iptables call in firewalld. I tried that some time ago and it worked nicely

Upstream commit:
https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=b3b451d6f8946986b8f50c8bcddeef50ed7a5f8f

*** This bug has been marked as a duplicate of bug 1161745 ***