Bug 2093423
| Summary: | state no longer required for masquerade and ICMP block inversion | |||
|---|---|---|---|---|
| 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 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | role:firewall | |||
| Fixed In Version: | rhel-system-roles-1.19.2-1.el9 | Doc Type: | Enhancement | |
| Doc Text: |
.The `firewall` RHEL System Role does not require the `state` parameter when configuring `masquerade` or `icmp_block_inversion`
When configuring custom firewall zones, variables `masquerade` and `icmp_block_inversion` are boolean settings. A value of `true` implies `state: present` and a value of `false` implies `state: absent`. Therefore, the `state` parameter is not required when configuring `masquerade` or `icmp_block_inversion`.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 2093437 (view as bug list) | Environment: | ||
| Last Closed: | 2022-11-15 10:23:47 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: | 2093437 | |||
|
Description
Rich Megginson
2022-06-03 16:22:49 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 |