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 2022461 - [RFE] - Firewall RHEL System Role should be able to set default zone
Summary: [RFE] - Firewall RHEL System Role should be able to set default zone
Keywords:
Status: CLOSED ERRATA
Alias: None
Deadline: 2022-02-22
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: rhel-system-roles
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.0
Assignee: Rich Megginson
QA Contact: Jakub Haruda
Malinga
URL:
Whiteboard: role:firewall
Depends On: 2022458
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-11 17:11 UTC by Brian Smith
Modified: 2022-05-17 19:03 UTC (History)
13 users (show)

Fixed In Version: rhel-system-roles-1.15.1-1.el9
Doc Type: Enhancement
Doc Text:
.The Firewall System Role now supports setting the firewall default zone Zones represent a concept to manage incoming traffic more transparently. The zones are connected to networking interfaces or assigned a range of source addresses. Firewall rules for each zone are managed independently enabling the administrator to define complex firewall settings and apply them to the traffic. This feature allows setting the default zone used as the default zone to assign interfaces to, same as `firewall-cmd --set-default-zone zone-name`.
Clone Of: 2022458
Environment:
Last Closed: 2022-05-17 13:03:10 UTC
Type: Bug
Target Upstream Version:
Embargoed:
vpunj: needinfo+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github linux-system-roles firewall pull 68 0 None Draft Add ability to set the default zone 2022-02-16 14:20:06 UTC
Red Hat Issue Tracker RHELPLAN-102548 0 None None None 2021-11-11 17:14:40 UTC
Red Hat Product Errata RHBA-2022:2443 0 None None None 2022-05-17 13:03:28 UTC

Description Brian Smith 2021-11-11 17:11:44 UTC
+++ This bug was initially created as a clone of Bug #2022458 +++

Description of problem:
The Firewall RHEL System Role should be able to set default zone (the equivalent of "firewall-cmd --set-default-zone zone-name")

The firewall System role will support creating new zones, and many customers will want to change the default zone to the newly created zone.

Comment 15 errata-xmlrpc 2022-05-17 13:03:10 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 (new packages: rhel-system-roles), 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:2443


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