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 1691821 - nft list parameters not documented
Summary: nft list parameters not documented
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nftables
Version: 8.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: alpha
: 8.1
Assignee: Phil Sutter
QA Contact: Jiri Peska
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-22 15:13 UTC by Tomas Dolezal
Modified: 2020-11-14 10:22 UTC (History)
4 users (show)

Fixed In Version: nftables-0.9.0-10.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 22:36:21 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3659 0 None None None 2019-11-05 22:36:34 UTC

Description Tomas Dolezal 2019-03-22 15:13:44 UTC
Description of problem:
some parameters for nft list are not well documented. plural forms are possible but not mentioned.
nft list tables
nft list counters
nft list quotas
nft list meters
nft list sets

Some options (table, chain) describe syntax for specific type (singular form) and name of object to be listed.
This description is missing in e.g. counters and quotas stateful object section.

Version-Release number of selected component (if applicable):
nftables-0.9.0-8.el8.x86_64

How reproducible:
always

Actual results:
e.g.
{delete | list | flush} table [family] table
{delete | list | flush} set [family] table set

well described:
{list | flush} ruleset [family]

Expected results:
each type/object that can be listed using list <type-plural> indicates so in it's section and/or in summarized examples

Additional info:

Comment 1 Fernando F. Mancera 2019-04-04 11:58:48 UTC
Hi, I have proposed this patch. What do you think? http://patchwork.ozlabs.org/patch/1077173/ Thanks.

Comment 2 Phil Sutter 2019-06-24 15:34:44 UTC
Hi Fernando,

(In reply to Fernando F. Mancera from comment #1)
> Hi, I have proposed this patch. What do you think?
> http://patchwork.ozlabs.org/patch/1077173/ Thanks.

Thanks for working on this!

Upstream commit to backport:

commit 067ac215e93f6cb912c3f99ca9e6689397bfba2f
Author: Fernando Fernandez Mancera <ffmancera>
Date:   Fri Apr 5 17:36:55 2019 +0200

    doc: update nft list plural form parameters
    
    Signed-off-by: Fernando Fernandez Mancera <ffmancera>
    Signed-off-by: Pablo Neira Ayuso <pablo>

Comment 6 errata-xmlrpc 2019-11-05 22:36:21 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, 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/RHEA-2019:3659


Note You need to log in before you can comment on or make changes to this bug.