Bug 2115154
| Summary: | support for firewall_config - gather firewall facts | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Rich Megginson <rmeggins> | |
| Component: | rhel-system-roles | Assignee: | Rich Megginson <rmeggins> | |
| Status: | CLOSED ERRATA | QA Contact: | Jakub Haruda <jharuda> | |
| Severity: | unspecified | Docs Contact: | Gabi Fialová <gfialova> | |
| Priority: | unspecified | |||
| Version: | 9.1 | CC: | gfialova, jharuda, nhosoi, spetrosi, vpunj | |
| Target Milestone: | rc | Keywords: | Triaged | |
| Target Release: | 9.1 | Flags: | pm-rhel:
mirror+
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | role:firewall | |||
| Fixed In Version: | rhel-system-roles-1.20.0-1.el9 | Doc Type: | Enhancement | |
| Doc Text: |
.The `firewall` RHEL System Role can provide Ansible facts
With this enhancement, you can now gather the `firewall` RHEL System Role's Ansible facts from all of your systems by including the `firewall:` variable in the playbook with no arguments. To gather a more detailed version of the Ansible facts, use the `detailed: true` argument, for example:
----
vars:
firewall:
detailed: true
----
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 2115160 (view as bug list) | Environment: | ||
| Last Closed: | 2022-11-15 10:24:00 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2115160 | |||
|
Description
Rich Megginson
2022-08-04 00:32:48 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-2022:8117 |