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 1917399

Summary: Rebase libnftnl to latest upstream version
Product: Red Hat Enterprise Linux 9 Reporter: Phil Sutter <psutter>
Component: libnftnlAssignee: Phil Sutter <psutter>
Status: CLOSED ERRATA QA Contact: Tomas Dolezal <todoleza>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.1CC: todoleza
Target Milestone: rcKeywords: Triaged, Upstream
Target Release: 9.1Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libnftnl-1.2.2-1.el9 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-15 11:19:39 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: 1917403    
Bug Blocks: 1917398, 2084543    

Description Phil Sutter 2021-01-18 12:34:11 UTC
Current upstream nftables release v0.9.8 requires libnftnl-1.1.9, RHEL8 still ships 1.1.5.

A few specific changes are present as well:
- debut output for set elements contains range end value in concatenated ranges
- bitwise expression debug output aligned with other expressions regarding
  register formatting

The second item above requires a small change in iptables testsuite.

Comment 3 Phil Sutter 2022-05-18 09:18:42 UTC
While being at it, I'll backport also one extra commit which is not part of 1.2.1 release:

commit e2514c0eff4da7e8e0aabd410f7b7d0b7564c880
Author: Florian Westphal <fw>
Date:   Sat Feb 19 14:39:04 2022 +0100

    exthdr: tcp option reset support
    
    Adds print debug support for tcp reset feature.
    
    Signed-off-by: Florian Westphal <fw>


This is a feature, but since the change replaces a generic "else" case, it actually fixes incorrect exthdr debug output for tcp option reset expressions.

Comment 4 Phil Sutter 2022-06-07 17:51:42 UTC
I'll reuse this ticket to rebase libnftnl once more, upstream released 1.2.2
today. It contains one additional fix (missing export of symbol
nftnl_set_elem_nlmsg_build_payload) and is a dependency of nftables 1.0.4 also
released today.

Comment 12 errata-xmlrpc 2022-11-15 11:19:39 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 (libnftnl 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-2022:8343