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:
When trying the new -W option, I have found some flaws handling the commandline.
Version-Release number of selected component (if applicable):
iptables-1.4.21-18.el7
How reproducible:
always
Steps to Reproduce:
1. iptables-restore -W
2. iptables-restore -W 0
3. iptables-restore --nonsense
Actual results:
1. # iptables-restore -W
dsfds
iptables-restore: line 1 failed
2. # iptables-restore -W 0
dssf
iptables-restore: line 1 failed
3. # iptables-restore --nonsense
iptables-restore: unrecognized option '--nonsense'
dsdsf
iptables-restore: line 1 failed
Expected results:
1. an error about missing value should be reported, program should exit without processing input
2. from man - "This option only works with -w." - so an error about missing "-w" should be reported and the program should exit without processing input
Plus I am not sure what sense makes setting this to 0, probably it should be rejected?
3. similar as above, the program should exit without processing input
Hi,
(In reply to Jiri Peska from comment #1)
> Description of problem:
> When trying the new -W option, I have found some flaws handling the
> commandline.
>
> Version-Release number of selected component (if applicable):
> iptables-1.4.21-18.el7
>
> How reproducible:
> always
>
> Steps to Reproduce:
> 1. iptables-restore -W
> 2. iptables-restore -W 0
> 3. iptables-restore --nonsense
>
> Actual results:
> 1. # iptables-restore -W
> dsfds
> iptables-restore: line 1 failed
>
> 2. # iptables-restore -W 0
> dssf
> iptables-restore: line 1 failed
>
> 3. # iptables-restore --nonsense
> iptables-restore: unrecognized option '--nonsense'
> dsdsf
> iptables-restore: line 1 failed
>
> Expected results:
> 1. an error about missing value should be reported, program should exit
> without processing input
>
> 2. from man - "This option only works with -w." - so an error about missing
> "-w" should be reported and the program should exit without processing input
>
> Plus I am not sure what sense makes setting this to 0, probably it should be
> rejected?
In RHEL8, these options are simply ignored by iptables-restore as locking is not needed anymore with nftables backend. They are accepted just to stay compatible with how iptables-restore may be invoked. Therefore I don't see any sense in adding code for validation.
> 3. similar as above, the program should exit without processing input
I can't reproduce this on RHEL8 with package iptables-1.8.0-8.el8.x86_64. Could you please verify this is a valid complaint?
Thanks, Phil