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:
When adding a zone in a list of other operations, you cannot use the newly added zone until the firewall config is reloaded. The problem is that the role takes a list of firewall settings:
firewall:
- zone: my_new_zone
state: present
- port: 54321
zone: my_new_zone
state: enabled
If you are using something like satellite, you do not have access to the playbook, so you cannot insert a task to reload between creating the zone and using the zone.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
When adding or removing a zone, the operation should take effect immediately, so that the zone can be used in subsequent operations in the list (or not if the zone was removed).
Additional info:
(In reply to Brian Smith from comment #1)
> @rmeggins Do we have a corresponding BZ for RHEL 8?
No, not yet. Let's have all of the discussion and whatnot here, then I will clone it, then the clone will have all of the discussion and etc.
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
Description of problem: When adding a zone in a list of other operations, you cannot use the newly added zone until the firewall config is reloaded. The problem is that the role takes a list of firewall settings: firewall: - zone: my_new_zone state: present - port: 54321 zone: my_new_zone state: enabled If you are using something like satellite, you do not have access to the playbook, so you cannot insert a task to reload between creating the zone and using the zone. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: When adding or removing a zone, the operation should take effect immediately, so that the zone can be used in subsequent operations in the list (or not if the zone was removed). Additional info: