Project

General

Profile

Actions

Bug #4551

closed

Initial logrotate configuration (from initial-promises) does not include recent fixes

Added by Jonathan CLARKE almost 9 years ago. Updated almost 9 years ago.

Status:
Released
Priority:
2
Category:
System techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Regression:

Description

The logrotate configuration files should be the same in initial promises and techniques. However, currently there are several differences.

This is really a low impact bug, since the initial promises don't get used for very long at all on a policy server, since a promise generation is almost the first thing that happens. However, this can cause unrequired repairs, and possibly variations in behaviour that could be confusing to debug.


Subtasks 2 (0 open2 closed)

Bug #4554: Initial logrotate configuration (from initial-promises) does not apply delaycompress optionReleasedJonathan CLARKE2014-03-05Actions
Bug #4556: Log file about non compliant reports is not managed by logrotate on Red Hat-like Rudder serverReleasedMatthieu CERDA2014-03-05Actions

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #4445: Wrong permissions slapd.log after logrotateReleasedJonathan CLARKE2014-02-06Actions
Actions #1

Updated by Jonathan CLARKE almost 9 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Jonathan CLARKE to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/307
Actions #2

Updated by Jonathan CLARKE almost 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset policy-templates:commit:2531625689f1c42352d49e6d34527108b1933a15.

Actions #3

Updated by Nicolas CHARLES almost 9 years ago

Applied in changeset policy-templates:commit:76d4b1363b7e00087abc2024fd3f1cccd8439330.

Actions #4

Updated by Vincent MEMBRÉ almost 9 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.6.11, which was released today.
Check out:

Actions

Also available in: Atom PDF