http://bugzilla.novell.com/show_bug.cgi?id=913421
--- Comment #8 from Dirk Weber
That's probably because the timer was inactive, perhaps because it failed to run the service unit? Does "systemctl list-timers --all" list the logrotate.timer? I can't tell any more if "systemctl list-timers --all" would have listed the logrotate.timer, I enabled it on all my systems in January. After enabling the timer and have it fire at a time while the machines are running log rotation worked. Therefore I think the issue is just that the timer is not running by default and not with the service unit.
We can use something similar to your solution from comment 1. it works fine for me for months.
-- You are receiving this mail because: You are on the CC list for the bug.