Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
1)
iptables-save --help/unknown parameter to iptables-save causes error message with reference to missing manpage / manpage of other name.
2)
iptables-restore refers to xtables-restore, which is also not present on system
Version-Release number of selected component (if applicable):
iptables-1.8.2-11.el8.x86_64
How reproducible:
always
Steps to Reproduce:
1)
# iptables-save --help
iptables-save: unrecognized option '--help'
Look at manual page `xtables-save.8' for more information.
2)
2nd related issue:
# iptables-restore --bad
iptables-restore: unrecognized option '--bad'
Try `xtables-restore -h' for more information.
Actual results:
* manpage is missing, however iptables-save and iptables-restore pages are provided
* xtables-restore is absent
Expected results:
* manpage symlink / corrected error message
* iptables-restore message should also be corrected to refer to available command
Additional info:
rpm -qd iptables
/usr/share/doc/iptables/INCOMPATIBILITIES
/usr/share/man/man8/ip6tables-restore.8.gz
/usr/share/man/man8/ip6tables-save.8.gz
/usr/share/man/man8/ip6tables.8.gz
/usr/share/man/man8/iptables-apply.8.gz
/usr/share/man/man8/iptables-extensions.8.gz
/usr/share/man/man8/iptables-restore.8.gz
/usr/share/man/man8/iptables-save.8.gz
/usr/share/man/man8/iptables.8.gz
/usr/share/man/man8/nfnl_osf.8.gz
/usr/share/man/man8/xtables-monitor.8.gz
/usr/share/man/man8/xtables-nft.8.gz
/usr/share/man/man8/xtables-translate.8.gz
Fix for iptables-save:
commit 934479aa1f1576afba97b137a101a60d8534370c
Author: Phil Sutter <phil>
Date: Wed Mar 13 20:46:17 2019 +0100
xtables-save: Point at existing man page in help text
Signed-off-by: Phil Sutter <phil>
Signed-off-by: Florian Westphal <fw>
A fix for iptables-restore has been sent upstream: https://marc.info/?l=netfilter-devel&m=156001526722299&w=2
Z-stream request must be a mistake, 8.1 isn't even released yet.
Patch has been accepted, second commit to backport on behalf of this bug:
commit ac531b4681d1a0309a738d7bc3408fc2270eaa03
Author: Phil Sutter <phil>
Date: Sat Jun 8 19:34:13 2019 +0200
xtables-restore: Fix program names in help texts
Avoid referring to wrong or even non-existent commands:
* When calling xtables_restore_main(), pass the actual program name
taken from argv[0].
* Use 'prog_name' in unknown parameter and help output instead of
'xtables-restore' which probably doesn't exist.
* While being at it, fix false whitespace in help text.
Signed-off-by: Phil Sutter <phil>
Signed-off-by: Pablo Neira Ayuso <pablo>
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