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 1871867 - Wrong prefix in ip6tables-nft error messages
Summary: Wrong prefix in ip6tables-nft error messages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: iptables
Version: 8.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 8.4
Assignee: Phil Sutter
QA Contact: Jiri Peska
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-24 14:01 UTC by Phil Sutter
Modified: 2021-05-18 14:59 UTC (History)
15 users (show)

Fixed In Version: iptables-1.8.4-17.el8
Doc Type: No Doc Update
Doc Text:
Clone Of: 1860518
Environment:
Last Closed: 2021-05-18 14:58:38 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 Product Errata RHBA-2021:1642 0 None None None 2021-05-18 14:59:08 UTC

Description Phil Sutter 2020-08-24 14:01:42 UTC 
Current RHEL8 ip6tables incorrectly prefixes error messages with 'iptables:' instead of 'ip6tables:' as it should (and legacy does).

Upstream fix to backport:

commit 3be40dcfb5af1438b6abdbda45a1e3b59c104e13
Author: Phil Sutter <phil>
Date:   Fri Aug 7 13:48:28 2020 +0200

    nft: Fix command name in ip6tables error message
    
    Upon errors, ip6tables-nft would prefix its error messages with
    'iptables:' instead of 'ip6tables:'. Turns out the command name was
    hard-coded, use 'progname' variable instead.
    While being at it, merge the two mostly identical fprintf() calls into
    one.
    
    Signed-off-by: Phil Sutter <phil>
    Acked-by: Pablo Neira Ayuso <pablo>

Related shell test enhancement to cover it:

commit cd3e83d1b04fd2683f0fb06e496ee5be08a96b4f
Author: Phil Sutter <phil>
Date:   Thu Aug 6 18:52:34 2020 +0200

    tests: shell: Merge and extend return codes test
    
    Merge scripts for iptables and ip6tables, they were widely identical.
    Also extend the test by one check (removing a non-existent rule with
    valid chain and target) and quote the error messages where differences
    are deliberately ignored.
    
    Signed-off-by: Phil Sutter <phil>
    Acked-by: Pablo Neira Ayuso <pablo>
Comment 14 errata-xmlrpc 2021-05-18 14:58:38 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 (iptables bug fix and enhancement update), 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-2021:1642
Note You need to log in before you can comment on or make changes to this bug.