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 2222433 - Check mode fails when creating new firewall service
Summary: Check mode fails when creating new firewall service
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rhel-system-roles
Version: 8.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.9
Assignee: Rich Megginson
QA Contact: David Jež
Gabi Fialová
URL:
Whiteboard: role:firewall
Depends On: 2222428
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-12 17:55 UTC by Rich Megginson
Modified: 2024-03-14 04:25 UTC (History)
7 users (show)

Fixed In Version: rhel-system-roles-1.22.0-0.16.el8
Doc Type: Bug Fix
Doc Text:
.Running the `firewall` RHEL System Role in check mode with non-existent services no longer fails Previously, running the `firewall` role in check mode with non-existent services would fail. This fix implements better compliance with Ansible best practices for check mode. As a result, non-existent services being enabled or disabled no longer fails the role in check mode. Instead, a warning prompts you to confirm that the service is defined in a previous playbook.
Clone Of: 2222428
Environment:
Last Closed: 2023-11-14 15:31:21 UTC
Type: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github linux-system-roles firewall pull 153 0 None Merged fix: make enabling/disabling non-existent services not fail in check mode 2023-07-12 18:01:07 UTC
Red Hat Issue Tracker RHELPLAN-162180 0 None None None 2023-07-12 17:57:20 UTC
Red Hat Product Errata RHEA-2023:6946 0 None None None 2023-11-14 15:31:37 UTC

Description Rich Megginson 2023-07-12 17:55:39 UTC 
+++ This bug was initially created as a clone of Bug #2222428 +++

When creating and enabling a service, using check mode will fail since the service does not exist - should issue a warning that the service does not exist - see https://github.com/linux-system-roles/firewall/issues/146
Comment 9 errata-xmlrpc 2023-11-14 15:31:21 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/RHEA-2023:6946
Comment 10 Red Hat Bugzilla 2024-03-14 04:25:59 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.