Bug 2166661 - avoid iptables flush if using nftables backend
Summary: avoid iptables flush if using nftables backend
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: firewalld
Version: 9.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Eric Garver
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 2221175
TreeView+ depends on / blocked
 
Reported: 2023-02-02 15:02 UTC by Eric Garver
Modified: 2023-07-07 12:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2221175 (view as bug list)
Environment:
Last Closed: 2023-04-27 14:41:41 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github firewalld firewalld pull 1082 0 None Merged feat(direct): avoid iptables flush if using nftables backend 2023-02-02 15:02:48 UTC
Red Hat Issue Tracker NP-641 0 None None None 2023-02-02 15:02:48 UTC
Red Hat Issue Tracker   RHEL-427 0 None None None 2023-07-07 12:29:47 UTC
Red Hat Issue Tracker RHELPLAN-156083 0 None None None 2023-04-28 18:35:28 UTC

Description Eric Garver 2023-02-02 15:02:49 UTC 
MicroShift needs this to avoid a conflict with iptables ownership.

https://issues.redhat.com/browse/NP-641
Comment 4 Eric Garver 2023-02-02 15:09:03 UTC 
Upstream commits:

dcd0dd3674ea ("test(direct): avoid iptables flush if using nftables backend")
b7faa74db15e ("feat(direct): avoid iptables flush if using nftables backend")
a5adb26a5eeb ("test(atlocal): pass EBTABLES to testsuite")
Comment 5 Eric Garver 2023-04-27 14:42:55 UTC 
This bug has been migrated to the Red Hat Issue Tracker (Jira). This bugzilla is obsolete. Any changes should be done in Jira.

https://issues.redhat.com/browse/RHEL-427
Comment 6 Eric Garver 2023-04-28 18:35:11 UTC 
(In reply to Eric Garver from comment #5)
> This bug has been migrated to the Red Hat Issue Tracker (Jira). This
> bugzilla is obsolete. Any changes should be done in Jira.

Reopened because Jira can't handle the zstream workflow yet.
Note You need to log in before you can comment on or make changes to this bug.