Bug 1498923
Summary: | If a direct rule fails to insert all following direct rules also fail | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Eric Garver <egarver> |
Component: | firewalld | Assignee: | Eric Garver <egarver> |
Status: | CLOSED ERRATA | QA Contact: | Tomas Dolezal <todoleza> |
Severity: | high | Docs Contact: | Mirek Jahoda <mjahoda> |
Priority: | high | ||
Version: | 7.4 | CC: | ajohn, atragler, egarver, mjahoda, shuali, todoleza, vdanek |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | firewalld-0.5.3-5.el7 | Doc Type: | Bug Fix |
Doc Text: |
*firewalld* now prevents partially applied rules
Previously, if a direct rule failed to be inserted for any reason, then all following direct rules with a higher priority also failed to insert. As a consequence, direct rules were not applied completely. The processing has been changed to either apply all direct rules successfully or revert them all. As a result, if a rule failure occurs at startup, *firewalld* enters the `failed` status and allows the user to remedy the situation. This prevents unexpected results by having partially applied rules.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-30 10:11:40 UTC | Type: | Bug |
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: | 1477664, 1554861 |
Description
Eric Garver
2017-10-05 14:46:30 UTC
Additionally fixes as per comment 9 through comment 13: f475bd2293b7 ("fw: if failure occurs during startup set state to FAILED") d3acaac62106 ("fw: on restart set policy from same function") 8b3591c3f238 ("tests/functions: check state after a reload") 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, 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-2018:3120 |