Bug 1689363

Summary: TestOnly: Fix inconvenient nft monitor command options
Product: Red Hat Enterprise Linux 8 Reporter: Phil Sutter <psutter>
Component: nftablesAssignee: Phil Sutter <psutter>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: medium    
Version: 8.1CC: rkhan, todoleza
Target Milestone: rcKeywords: TestOnly
Target Release: 8.2Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nftables-0.9.2-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:41:51 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:

Description Phil Sutter 2019-03-15 17:41:58 UTC
Enabling JSON output in nft monitor should be possible via '-j' flag or at least 'nft monitor json', not 'nft monitor vm json' as it is now in RHEL8.

Upstream, there is 'nft monitor json'. Ideally '-j' should be respected and 'json' parameter be deprecated.

Comment 1 Phil Sutter 2019-06-12 17:30:10 UTC
Fix sent upstream: https://marc.info/?l=netfilter-devel&m=156036046227680&w=2

Comment 2 Phil Sutter 2019-06-24 14:35:32 UTC
Upstream commit to backport:

mmit cc1ea7ef36868c0708741392c99fcd2f2c395131
Author: Phil Sutter <phil>
Date:   Wed Jun 12 19:27:37 2019 +0200

    monitor: Accept -j flag
    
    Make 'nft -j monitor' equal to 'nft monitor json' and change
    documentation to use only the first variant since that is more intuitive
    and also consistent with other commands.
    
    While being at it, drop references to XML from monitor section - it was
    never supported.
    
    Signed-off-by: Phil Sutter <phil>
    Signed-off-by: Pablo Neira Ayuso <pablo>

Comment 3 Phil Sutter 2019-10-30 19:16:18 UTC
Implicitly resolved by rebase.

Comment 4 Phil Sutter 2019-10-30 19:17:53 UTC
Tomas,

Can we cover for this in RHEL-8.2.0? For testing, it should suffice to make sure that 'nft -j monitor' will print JSON output.

Cheers, Phil

Comment 7 errata-xmlrpc 2020-04-28 16:41:51 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-2020:1774