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.
Bug 2057172 - ensure target changes take effect immediately
Summary: ensure target changes take effect immediately
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rhel-system-roles
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.6
Assignee: Rich Megginson
QA Contact: David Jež
Gabi Fialová
URL:
Whiteboard: role:firewall
Depends On: 2057164
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-22 20:56 UTC by Rich Megginson
Modified: 2022-05-10 14:41 UTC (History)
6 users (show)

Fixed In Version: rhel-system-roles-1.15.0-1.el8
Doc Type: Bug Fix
Doc Text:
.The Firewall System Role now reloads the firewall immediately when `target` changes Previously, the Firewall System Role was not reloading the firewall when the `target` parameter has been changed. With this fix, the Firewall role reloads the firewall when the `target` changes, and as a result, the `target` change is immediate and available for subsequent operations.
Clone Of: 2057164
Environment:
Last Closed: 2022-05-10 14:13:20 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github linux-system-roles firewall pull 70 0 None Merged ensure that changes to target take effect immediately 2022-02-22 21:03:15 UTC
Red Hat Issue Tracker RHELPLAN-113123 0 None None None 2022-02-22 21:01:59 UTC
Red Hat Product Errata RHBA-2022:1896 0 None None None 2022-05-10 14:14:46 UTC

Description Rich Megginson 2022-02-22 20:56:31 UTC
+++ This bug was initially created as a clone of Bug #2057164 +++

Description of problem:

With the firewall role, after changing the zone target with a playbook like the following, I have to manually reload the firewall for the change to take affect after running the playbook:  

- name: Change public zone target to DROP
  hosts: localhost

  vars:
    firewall:
      zone: public
      state: enabled
      permanent: yes
      target: DROP 
  roles:
    - rhel-system-roles.firewall



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 10 errata-xmlrpc 2022-05-10 14:13:20 UTC
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 (rhel-system-roles 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:1896


Note You need to log in before you can comment on or make changes to this bug.