Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2211063

Summary: Rebase package to upstream version 1.8.5
Product: Red Hat Enterprise Linux 8 Reporter: Phil Sutter <psutter>
Component: iptablesAssignee: Phil Sutter <psutter>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact: Marc Muehlfeld <mmuehlfe>
Priority: unspecified    
Version: 8.9CC: bpanchal, egarver, jbainbri, jpeska, todoleza
Target Milestone: rcKeywords: Triaged
Target Release: 8.9Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: iptables-1.8.5-8.el8 Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
.`iptables` rebased to version 1.8.5 The `iptables` packages have been upgraded to upstream version 1.8.5, which provides a number of enhancements and bug fixes over the previous version: * The code of the `iptables-apply` script was cleaned up. * Missing translations were added, and existing translations were fixed in the `iptables-translate` utility. Additionally, translations were reviewed for strictness. As a result, API users can now notice if a translation fails. * The `connlabel` match operation now supports numeric labels. * The cache handling was improved: ** The kernel rule set caching code was rewritten. ** The `iptables` utility gathers the initial requirements before fetching the needed data. ** If possible, `iptables` now caches only specific chains and tables. * In `bpf` match operations, `iptables` opens Extended Berkeley Packet Filter (eBPF) programs in read-only mode. * The `--alarm` option was added to the `IDLETIMER` target. * Multiple memory leaks were fixed. * Code was merged to reduce the size and optimize the code flow. * The string match extension no longer prints the `--to` option if its value is the default one. * The `among` match extension was fixed to work correctly when used in multiple rules loaded by the `ebtables-restore` utility. * Various man pages were updated.
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-14 15:51:50 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: 2174395, 2190094    
Deadline: 2023-08-14   

Description Phil Sutter 2023-05-30 12:21:12 UTC
The current iptables-1.8.4-24.el8 contains 78 distinct backports from upstream.
A caching issue reported in bug 2190094 required an additional 29 backports to
resolve, mainly a cache-related refactoring which went into upstream's v1.8.5
release. The risk and testing overhead involved with backporting these commits
out of order makes up for that of a rebase, so we'll do the latter instead:

Rebase onto v1.8.5 plus the fixes upstream identified using 'Fixes:' tag and
all of the previous 78 backports not already present. To reduce merge
conflicts, sort them by commit date.

Comment 1 Phil Sutter 2023-05-30 12:36:15 UTC
Use the opportunity for a bit of spec file cleanup:

* Drop the bootstrap code needed when libiptc SONAME bumped in RHEL8.2
* Eliminate a duplicate file warning caused by overlapping globbing in %files
  section

Comment 2 Phil Sutter 2023-05-30 12:39:12 UTC
Changes proposed here: https://gitlab.com/redhat/centos-stream/rpms/iptables/-/merge_requests/36

Comment 12 Phil Sutter 2023-09-01 11:54:30 UTC
This rebase causes a regression, reported in bug 2236501. The fix is a commit
which lacks a Fixes: tag and therefore wasn't identified by my script.

I went through the list of upstream commits since v1.8.5, manually searching
for the word "fix". I identified two regression fixes which affect us:

0bd7a8eaf3582 ("iptables-nft: fix basechain policy configuration")
- The reported fix in bug 2236501
- Test case included

30c1d44389631 ("ebtables: Exit gracefully on invalid table names")
- Fix abort when specifying invalid table name
- Affects error path only

It looks like we need exception+ now to push a new build. Should we try or do
an early z-stream after GA?

Comment 13 Eric Garver 2023-09-01 12:46:32 UTC
> It looks like we need exception+ now to push a new build. Should we try or do
an early z-stream after GA?

It could be 0day zstreamed.

Comment 18 Phil Sutter 2023-09-19 10:58:09 UTC
Dropped a left-over from your corrections, please review.

Comment 21 errata-xmlrpc 2023-11-14 15:51:50 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 (iptables 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/RHBA-2023:7184