Bug #4556
closed
Bug #4551: Initial logrotate configuration (from initial-promises) does not include recent fixes
Log file about non compliant reports is not managed by logrotate on Red Hat-like Rudder server
Added by Jonathan CLARKE over 10 years ago.
Updated over 10 years ago.
Category:
System techniques
Description
Issue #3073 added a logrotate configuration for the file /var/log/rudder/compliance/non-compliant-reports.log. It is missing in the RHEL version of the logrotate config.
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Matthieu CERDA
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/310
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:2a6fe3e1072e6255d322048d85d62144b0650258.
Applied in changeset policy-templates:commit:594aea672b537b78969ec3312e2d01a23338e953.
- Subject changed from Initial logrotate configuration (from initial-promises) does not include fix for #3073 to Log file about non compliant reports is not managed by logrotate on redhat like Rudder server
- Subject changed from Log file about non compliant reports is not managed by logrotate on redhat like Rudder server to Log file about non compliant reports is not managed by logrotate on Red Hat-like Rudder server
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.11, which was released today.
Check out:
Also available in: Atom
PDF
Updated by Jonathan CLARKE 
Updated by Matthieu CERDA 
Updated by