Bug 1321980 - Logrotate doesn't rotate logs if /var/lib/logrotate.status is corrupted
Summary: Logrotate doesn't rotate logs if /var/lib/logrotate.status is corrupted
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: logrotate
Version: 7.2
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 447022
TreeView+ depends on / blocked
 
Reported: 2016-03-29 13:57 UTC by Tomas Dolezal
Modified: 2018-09-12 07:23 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Needless to document.
Clone Of: 447022
Environment:
Last Closed: 2016-07-11 11:45:58 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1374550 0 medium CLOSED After a failure, logrotate doesn't clean up its incomplete work, leaving it in an unrunnable state 2021-02-22 00:41:40 UTC

Internal Links: 1374550

Comment 5 Kamil Dudka 2016-06-28 14:21:46 UTC
This is caused by the following upstream commit:

https://github.com/logrotate/logrotate/commit/r3-8-5~20

... which intentionally reverted the original fix:

https://github.com/logrotate/logrotate/commit/r3-7-8~11

Should we revert the revert to get this fixed?

Comment 6 Kamil Dudka 2016-06-30 11:25:08 UTC
Honza is fine with reverting the revert for RHEL-7.  There is still a question how to solve this properly in upstream.  We also need to discover why the file gets corrupted.

Comment 10 Kamil Dudka 2016-07-11 10:36:01 UTC
The fix for this bug causes a regression: bug #1354203 comment #15

I will revert the fix and remove this bug from the RHEL-7.3 erratum.

Comment 12 Kamil Dudka 2016-07-11 11:45:58 UTC
The fix for this bug introduces a change in behavior, which we try to avoid in RHEL.  Additionally, it already caused a regression (bug #1354203 comment #15).  I am closing this bug as WONTFIX.  Feel free to reopen if you have a business justification for it.


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