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.
Bug 1754117 - firewalld logs are not rotated
Summary: firewalld logs are not rotated
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: firewalld
Version: 7.7
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Eric Garver
QA Contact: Tomas Dolezal
Marc Muehlfeld
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-20 20:48 UTC by Robert McSwain
Modified: 2023-10-06 18:35 UTC (History)
3 users (show)

Fixed In Version: firewalld-0.6.3-10.el7
Doc Type: Bug Fix
Doc Text:
.RHEL rotates `firewalld` log files Previously, RHEL did not rotate `firewalld` log files. As a consequence, the `/var/log/firewalld` log file grew indefinitely. This update adds the `/etc/logrotate.d/firewalld` log rotation configuration file for the `firewalld` service. As a result, the `/var/log/firewalld` log is rotated, and users can customize the rotation settings in the `/etc/logrotate.d/firewalld` file.
Clone Of:
Environment:
Last Closed: 2020-09-29 19:21:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:3863 0 None None None 2020-09-29 19:21:27 UTC

Description Robert McSwain 2019-09-20 20:48:07 UTC
Description of problem:
as long as logs are not rotated they will grow indefinitely and eventually take unnecessary amounts of disk space, it'd seem best to add log rotation regardless in an upcoming version.

Version-Release number of selected component (if applicable):
RHV-M 4.2.8 and 4.3.5, and the latest hypervisors for both releases

How reproducible:
100%

Steps to Reproduce:
1. Install the hypervisor and observe that firewall logs do not rotate. 
2. Observe that there is no policy to rotate logs in /etc/logrotate.d/

Actual results:
Logs grow indefinitely

Expected results:
Logs rotate once a week or more

Comment 1 Sandro Bonazzola 2019-09-23 06:47:08 UTC
Moving this to platform firewalld component. Assuming this is a real issue, it should be solved at platform level.

Comment 10 Eric Garver 2020-02-19 12:56:19 UTC
upstream:

   bd17df59bc34 ("fix: add logrotate policy")

Comment 21 errata-xmlrpc 2020-09-29 19:21: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 (firewalld bug fix and enhancement update), 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/RHBA-2020:3863


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