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.
The same error also applies to SETS
# nft list set mytable myset
table ip mytable {
set myset {
type inet_service
elements = { 63, bootpc, tftp, snpp }
}
}
# nft flush set mytable myset
Error: Could not process rule: Invalid argument
flush set mytable myset
^^^^^^^^^^^^^^^^^^^^^^^^
This looks like a duplicate of Bug 1576465, which is a kernel issue. I guess it makes sense to keep this open to make sure we're fine on userspace side.
The issue reported here was fixed in kernel space (tracked by bug 1576465). That fix is available since kernel-3.10.0-1018.el7, so I'm turning this into a TestOnly issue.
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-2019:2215
Description of problem: flushing a map is not possible: Error: Could not process rule: Invalid argument Version-Release number of selected component (if applicable): nftables-0.8-10.el7.x86_64 How reproducible: always Steps to Reproduce: set -x nft add table mytable nft add table ip6 mytable6 nft add map ip mytable mymap4 { type inet_proto : mark \; } nft add map ip6 mytable6 mymap6 { type inet_proto : mark \; } nft list map ip mytable mymap4 nft list map ip6 mytable6 mymap6 nft flush map ip mytable mymap4 nft flush map ip6 mytable6 mymap6 nft delete map ip mytable mymap4 nft delete map ip6 mytable6 mymap6 Actual results: + nft add table mytable + nft add table ip6 mytable6 + nft add map ip mytable mymap4 '{' type inet_proto : mark ';' '}' + nft add map ip6 mytable6 mymap6 '{' type inet_proto : mark ';' '}' + nft list map ip mytable mymap4 table ip mytable { map mymap4 { type inet_proto : mark } } + nft list map ip6 mytable6 mymap6 table ip6 mytable6 { map mymap6 { type inet_proto : mark } } + nft flush map ip mytable mymap4 Error: Could not process rule: Invalid argument flush map ip mytable mymap4 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + nft flush map ip6 mytable6 mymap6 Error: Could not process rule: Invalid argument flush map ip6 mytable6 mymap6 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + nft delete map ip mytable mymap4 + nft delete map ip6 mytable6 mymap6 Expected results: Additional info: