Bug 1682994

Summary:	[RHEL8] TestOnly: nft list counters doesn't work
Product:	Red Hat Enterprise Linux 8	Reporter:	yiche <yiche>
Component:	nftables	Assignee:	Phil Sutter <psutter>
Status:	CLOSED DUPLICATE	QA Contact:	qe-baseos-daemons
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	CC:	jiji, rkhan, todoleza
Target Milestone:	rc	Keywords:	TestOnly
Target Release:	8.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	nftables-0.9.0-9.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-02 16:19:46 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:	1682337
Bug Blocks:

Comment 1 Phil Sutter 2019-02-26 11:54:17 UTC

Upstream fix to backport:

commit dafac7d528de0890b82f943fc818ccb7a82fca7d
Author: Florian Westphal <fw>
Date:   Wed Jan 2 17:10:36 2019 +0100

    rule: fix object listing when no table is given
    
    'nft list quotas' would not print anything at all anymore.
    
    Fixes: 88456a7ef01172 ("rule: list only the table containing object")
    Signed-off-by: Florian Westphal <fw>

Not critical enough to justify a blocker this late in schedule IMHO, hence moving to RHEL8.1. Feel free to reset in case you disagree.

Thanks, Phil

Comment 2 Tomas Dolezal 2019-03-22 15:15:19 UTC

syntax of the list commands does not cover counters from comment 0, filed separate bug 1691821 for manpage documentation because there are more types to cover than counters.

Comment 3 Phil Sutter 2019-07-02 16:16:46 UTC

Fix already backported as part of Bug 1721720.

Comment 4 Phil Sutter 2019-07-02 16:19:46 UTC

(In reply to Phil Sutter from comment #3)
> Fix already backported as part of Bug 1721720.

Given that testing instructions exist for each commit backported on behalf of Bug 1721720 there is no added value in keeping this open.

*** This bug has been marked as a duplicate of bug 1721720 ***