Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1507197 - Do not use log rotation for /var/log/boot.log
Do not use log rotation for /var/log/boot.log
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: plymouth (Show other bugs)
7.4
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Ray Strode [halfline]
Desktop QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-10-28 03:21 EDT by Amey
Modified: 2018-04-10 14:39 EDT (History)
2 users (show)

See Also:
Fixed In Version: plymouth-0.8.9-0.30.20140113.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 14:38:54 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0999 None None None 2018-04-10 14:39 EDT

  None (edit)
Description Amey 2017-10-28 03:21:02 EDT
Description of problem:

boot.log is rotated by a /etc/logrotate.d/bootlog (owned by plymouth package). It rotates daily even if empty. The default behaviour should be to rotate notifempty, or only on boot.
NOTE: This was corrected in RHEL6 via https://bugzilla.redhat.com/show_bug.cgi?id=683537 but has regressed in RHEL7


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


How reproducible:

always

Steps to Reproduce:

below the file from RHEL 7.4
++
[root@rhel7u4-2 ~]# cat /etc/logrotate.d/bootlog 
/var/log/boot.log
{
    missingok
    daily
    copytruncate
    rotate 7
}
++

Actual results:
/var/log/boot.log rotated due to /etc/logrotate.d/bootlog which is present as part of installation

Expected results:

/var/log/boot.log should not be rotated daily



Additional info:
n/a
Comment 6 errata-xmlrpc 2018-04-10 14:38:54 EDT
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://access.redhat.com/errata/RHBA-2018:0999

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