Enable configuring journald to purge logs based on time

Bug #1771573 reported by Juan Antonio Osorio Robles on 2018-05-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
High
Unassigned

Bug Description

Our current journald configuration in OSP Director is using the defaults, which handles rotation based off of log size and number of rotated logs. For things such as GDPR, we need to be able to define the retention based on age as the logs may contain personally identifiable information that needs to be deleted on demand (within a window of time). Ideally, we would only retain logs for <1M (2 weeks might be appropriate), with the option to configure the policy differently via Director.

This would be done by setting the MaxRetentionSec option in journald.conf

Changed in tripleo:
status: New → Triaged
importance: Undecided → Critical
milestone: none → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → rocky-rc2
Alex Schultz (alex-schultz) wrote :

Dropping to high as it does not properly fit in the Critical criteria of blocking a gate or preventing a deployment.

Changed in tripleo:
importance: Critical → High
milestone: rocky-rc2 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Changed in tripleo:
milestone: stein-2 → stein-3
Changed in tripleo:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers