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 2219873

Summary: RFE: Sets with quota elements are possible from the packet path in RHEL9 but impossible from the older nft that ships with RHEL9
Product: Red Hat Enterprise Linux 9 Reporter: Chris Barton <progeny-ethers.0p>
Component: nftablesAssignee: Phil Sutter <psutter>
Status: CLOSED MIGRATED QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: unspecified    
Version: 9.2CC: todoleza
Target Milestone: rcKeywords: FutureFeature, MigratedToJIRA, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-21 10:16:48 UTC Type: Story
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Chris Barton 2023-07-05 16:05:15 UTC
Description of problem: 
Sets with quota elements are possible from the packet path in RHEL9 but impossible from the older nft that ships with RHEL9

Version-Release number of selected component (if applicable):
nftables-1.0.4-10.el9_1.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Use nft -f to load the following
ROOT rhel9 ~% cat /etc/sysconfig/nftables
table ip filter {
        set outbound_quota {
                type ipv4_addr
                size 65535
                flags dynamic
                elements = { 10.0.0.44 quota over 200 mbytes }
        }
}

Actual results:
ROOT rhel9 ~% nft -f /etc/sysconfig/nftables
/etc/sysconfig/nftables:6:40-44: Error: syntax error, unexpected quota, expecting comma or '}'
                elements = { 10.0.0.44 quota over 200 mbytes }
                                       ^^^^^
Expected results:
The element should load with nft $?=0

Additional info:
Loading the same element is possible in RHEL9 via the packet path
        chain OUTPUT {
                type filter hook output priority filter; policy accept;
                add @outbound_quota { ip saddr quota over 200 mbytes } drop
        }

When I build and install nftables-1.0.7-1.fc39.src.rpm from Fedora rawhide, the problem goes away and the element with a quota loads successfully via nft -f.

Comment 1 Phil Sutter 2023-07-06 11:54:00 UTC
Probably resolved by backporting the simple commit 9cb501168a623 ("parser_bison: allow to use quota in sets"). I don't see a respective patch for JSON parser though, maybe upstream lacks this feature entirely.

Comment 3 RHEL Program Management 2023-09-21 10:16:28 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 4 RHEL Program Management 2023-09-21 10:16:48 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.