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 1679124 - iptables-translate manpages unavailable
Summary: iptables-translate manpages unavailable
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: iptables
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.1
Assignee: Phil Sutter
QA Contact: Jiri Peska
URL:
Whiteboard:
Depends On: 1682316
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-20 12:01 UTC by Tomas Dolezal
Modified: 2020-11-14 11:03 UTC (History)
5 users (show)

Fixed In Version: iptables-1.8.2-15.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 22:17:43 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:3573 0 None None None 2019-11-05 22:17:52 UTC

Description Tomas Dolezal 2019-02-20 12:01:48 UTC
Description of problem:
there is a joint manpage xtables-translate(8) for iptables-translate and others: ip{,6}tables-{restore-,}translate

the callable executables above actually don't have their respective manpage entries which would link to the joint manpage.

Version-Release number of selected component (if applicable):
iptables-1.8.2-9.el8.

How reproducible:
always

Steps to Reproduce:
for i in ip{,6}tables-{restore-,}translate xtables-translate; do man $i >/dev/null && echo "$i present"; done
No manual entry for iptables-restore-translate
No manual entry for iptables-translate
No manual entry for ip6tables-restore-translate
No manual entry for ip6tables-translate
xtables-translate present

Expected results:
all manpage entries lead to a manpage

Additional info:

Comment 1 Phil Sutter 2019-02-20 13:19:41 UTC
I agree, having man pages present for those definitely helps users. Fix sent upstream:

https://marc.info/?l=netfilter-devel&m=155066777401098&w=2

Aiming at RHEL8.1 for this one, it's no big issue IMHO. Feel free to protest in case you disagree.

Thanks, Phil

Comment 2 Phil Sutter 2019-06-12 16:57:00 UTC
Upstream commit to backport:

commit b738ca36777851e8f08c20a1e6c5c6492e934b38
Author: Phil Sutter <phil>
Date:   Wed Feb 20 14:02:55 2019 +0100

    doc: Install ip{6,}tables-translate.8 manpages
    
    These are just semantic links to xtables-translate.8.
    
    Signed-off-by: Phil Sutter <phil>
    Signed-off-by: Florian Westphal <fw>

Testing should be quite easy, just make sure ip{6,}tables{-restore,}-translate man pages exist.

Comment 10 errata-xmlrpc 2019-11-05 22:17:43 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:3573


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