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:
Errors and warnings are not printed on stderr, but stdout. This is not expected behaviour.

Version-Release number of selected component (if applicable):
scratch pre-build for 7.3 based on firewalld-0.4.3.2-1

How reproducible:
always

Steps to Reproduce:
1../firewall-cmd --remove-service=foo > /dev/null

Actual results:
Nothing

Expected results:
Error: INVALID_SERVICE: foo

Granting devel-ack for 7.3.

Fixed upstream: https://github.com/t-woerner/firewalld/commit/16b62b790a33022c27d408e897c0a6bf23cf2e36

An additional upstream fix is needed to hide errors and warnings printed to stderr in the firewalld test suite:

https://github.com/t-woerner/firewalld/commit/560a0e4e9f66da97ceeb69f295a989251e86a342

I think it would be good to add these two additional fixes for systems, where firewalld.conf is missing or has been removed:

firewall.core.logger: Warnings should be printed to stderr per default
https://github.com/t-woerner/firewalld/commit/db98f3b50301027cc822c87ffdc1a75671e9486b

test-suite: Ignore stderr to get default zone also for missing firewalld.conf
https://github.com/t-woerner/firewalld/commit/c51c0ef4dc7e440b0bc2d846f9810aa366699697

The first patch makes the behaviour consistent to firewall.command and the second pipes the stderr output to /dev/null. With these two patches the offline test suite is functional if firewalld.conf is missing.

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/RHSA-2016-2597.html