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:
doing a change to runtime configuration is not reflected in permanent scope after calling --runtime-to-permanent. Instead, success is reported and a warning message printed: Warning: NOT_ENABLED: eth0
DEBUG message (see Additional info) mentions zone block which is not anywhere used: the config is stock one provided by rpm.
Version-Release number of selected component (if applicable):
firewalld-1.1.1-2.el9.noarch
How reproducible:
always
Steps to Reproduce:
firewall-cmd --add-service smtp
firewall-cmd --runtime-to-permanent
firewall-cmd --reload
Actual results:
firewall-cmd --runtime-to-permanent
Warning: NOT_ENABLED: eth0
success
(EC=0)
Expected results:
Additional info:
nmcli con show eth0 | grep connection.zone
connection.zone: --
cp /var/log/firewalld /var/log/firewalld-2
firewall-cmd --runtime-to-permanent
cp /var/log/firewalld /var/log/firewalld-3
diff -U0 firewalld-{2,3} | tail
+2022-08-01 11:08:59 DEBUG1: IcmpType 'unknown-header-type' is identical, ignoring.
+2022-08-01 11:08:59 DEBUG1: getIcmpTypeSettings(unknown-option)
+2022-08-01 11:08:59 DEBUG1: config.getIcmpTypeByName('unknown-option')
+2022-08-01 11:08:59 DEBUG1: config.icmptype.44.getSettings()
+2022-08-01 11:08:59 DEBUG1: IcmpType 'unknown-option' is identical, ignoring.
+2022-08-01 11:08:59 DEBUG1: config.getIPSetNames()
+2022-08-01 11:08:59 DEBUG1: config.getZoneNames()
+2022-08-01 11:08:59 DEBUG1: getZoneSettings2(block)
+2022-08-01 11:08:59 DEBUG1: Zone 'block': interface binding for 'eth0' has been added by NM, ignoring.
+2022-08-01 11:08:59 WARNING: NOT_ENABLED: eth0
no other warnings or higher
Confirmed also on fedora-rawhide firewalld v1.2.0
my comment from GH issue:
>The issue is not occurring when NetworkManager kept stopped during firewalld start and the --runtime-to-permanent call. Starting NetworkManager even after firewalld restart causes the bug to reappear.
(tested on semi-up2date rawhide test vm)
Upstream commits:
f4f67413e4db ("test(runtimeToPermanent): verify when NM interfaces present")
15f47354c4a0 ("fix(runtimeToPermanent): errors for interfaces not in zone")
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (firewalld bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:8389
Description of problem: doing a change to runtime configuration is not reflected in permanent scope after calling --runtime-to-permanent. Instead, success is reported and a warning message printed: Warning: NOT_ENABLED: eth0 DEBUG message (see Additional info) mentions zone block which is not anywhere used: the config is stock one provided by rpm. Version-Release number of selected component (if applicable): firewalld-1.1.1-2.el9.noarch How reproducible: always Steps to Reproduce: firewall-cmd --add-service smtp firewall-cmd --runtime-to-permanent firewall-cmd --reload Actual results: firewall-cmd --runtime-to-permanent Warning: NOT_ENABLED: eth0 success (EC=0) Expected results: Additional info: nmcli con show eth0 | grep connection.zone connection.zone: -- cp /var/log/firewalld /var/log/firewalld-2 firewall-cmd --runtime-to-permanent cp /var/log/firewalld /var/log/firewalld-3 diff -U0 firewalld-{2,3} | tail +2022-08-01 11:08:59 DEBUG1: IcmpType 'unknown-header-type' is identical, ignoring. +2022-08-01 11:08:59 DEBUG1: getIcmpTypeSettings(unknown-option) +2022-08-01 11:08:59 DEBUG1: config.getIcmpTypeByName('unknown-option') +2022-08-01 11:08:59 DEBUG1: config.icmptype.44.getSettings() +2022-08-01 11:08:59 DEBUG1: IcmpType 'unknown-option' is identical, ignoring. +2022-08-01 11:08:59 DEBUG1: config.getIPSetNames() +2022-08-01 11:08:59 DEBUG1: config.getZoneNames() +2022-08-01 11:08:59 DEBUG1: getZoneSettings2(block) +2022-08-01 11:08:59 DEBUG1: Zone 'block': interface binding for 'eth0' has been added by NM, ignoring. +2022-08-01 11:08:59 WARNING: NOT_ENABLED: eth0 no other warnings or higher