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 1689363 - TestOnly: Fix inconvenient nft monitor command options
Summary: TestOnly: Fix inconvenient nft monitor command options
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nftables
Version: 8.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.2
Assignee: Phil Sutter
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-15 17:41 UTC by Phil Sutter
Modified: 2023-03-07 12:43 UTC (History)
2 users (show)

Fixed In Version: nftables-0.9.2-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:41:51 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-29159 0 None None None 2023-03-07 12:42:59 UTC
Red Hat Product Errata RHEA-2020:1774 0 None None None 2020-04-28 16:42:10 UTC

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


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