Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1357050 - exit codes don't match error messages in firewall-cmd
Summary: exit codes don't match error messages in firewall-cmd
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: firewalld
Version: 7.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Thomas Woerner
QA Contact: Tomas Dolezal
Depends On:
TreeView+ depends on / blocked
Reported: 2016-07-15 15:06 UTC by Tomas Dolezal
Modified: 2016-11-03 21:03 UTC (History)
1 user (show)

Fixed In Version: firewalld-
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-11-03 21:03:17 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2597 normal SHIPPED_LIVE Moderate: firewalld security, bug fix, and enhancement update 2016-11-03 12:11:47 UTC

Description Tomas Dolezal 2016-07-15 15:06:34 UTC
Description of problem:
error message and exit code of firewall-cmd does not match

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
[root@vm-rhel7s ~]# firewall-cmd --add-rich-rule 'rule family=ipv4 service name=dns limit value=4/d accept' --zone inexistent_zone; echo EC=$?
Error: INVALID_ZONE: inexistent_zone

[root@vm-rhel7s ~]# firewall-cmd --add-rich-rule 'rule family=ipv4 service name=dns limit value=1/d accept' ; echo EC=$?
Error: INVALID_LIMIT: 1/d too slow

Actual results:
bad exitcodes: 254 ~ UNKNOWN

Expected results:
exitcodes are according to manpage and the name of the error

Additional info:

Comment 7 errata-xmlrpc 2016-11-03 21:03:17 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.

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