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:
manpage: log level is not much described and it seems to be optional.
But log level is mandatory in the cmd tool.

Version-Release number of selected component (if applicable):
That's rfe.

How reproducible:
always

Steps to Reproduce:
1.log level is mandatory
but man page says: [level="log level"] ~ optional

2. Whats the log level?, is it for firewalld or rsyslog?

Actual results:
Its mandatory.
Description of these levels.

Expected results:
1,
edit man that's mandatory
or
make some log level default

2, please add into man page tiny description about each log level values. Or where to find (like see man syslog ... )

Additional info:

(In reply to Petr Sklenar from comment #0)
> But log level is mandatory in the cmd tool.

Should be optional. Fixed upstream with
https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=ffe3dc00e103ebe6a0ac83c880456ab31f0d09fb
 
> 2, please add into man page tiny description about each log level values. Or
> where to find (like see man syslog ... )

Added with
https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=323db01cb507d0040da9585deb61b712d1b3901c

firewalld-0.3.9-3.el7.noarch partly verified

Jirko, would it be possible to amend the manpage firewalld.richlanguage(5) with the default loglevel? I've found it to be 4:warning.

What about ?

Log level can be one of "emerg", "alert", "crit", "error", "warning", "notice", "info" or "debug", where default (i.e. if there's no one specified) is "warning".

https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=3f1b42f3b87e64f384aa9fc508d8ef9dfd59b56c

Ok, this seems reasonable for me :)

please update bug status accordingly to make sure that ON_QA is not set until the package is rebuilt sometime, thanks.

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://rhn.redhat.com/errata/RHBA-2015-0520.html