Bug #4401
closed
Rudder max days of archived reports retained cannot be configured from properties
Added by Matthieu CERDA about 10 years ago.
Updated about 10 years ago.
Category:
Web - Maintenance
Description
Rudder seems to ignore the rudder.batch.reportscleaner.archive.TTL property, when I set it to "15" to speed up the archiving on a loaded machine, it stays at "30" in the Web UI (which is the default value).
I don't know if either the value is not taken into account, or just wrongly displayed !
- Priority changed from 3 to 1
Nicolas or Vincent, can you please look into this asap? This could cause huge volumes of data to be stored for no reason, and that is expensive.
- Status changed from 8 to In progress
- Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
- Target version set to 2.6.11
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/438
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Assignee changed from François ARMAND to Vincent MEMBRÉ
Guys - fixing the bug is great, but we really need to know more. This sounds pretty serious from the title.
Please clarify: what was the previous behaviour (before bug fix) and how did changing the rudder.batch.reportscleaner.archive.TTL setting affect it (if at all)?
The previous behaviour was to ignore the parameter and always use the default value (what we had thought based on what user reported).
- Subject changed from Rudder seems to ignore the rudder.batch.reportscleaner.archive.TTL property to Rudder ignores the rudder.batch.reportscleaner.archive.TTL property and defaults to 30 days
Thanks for clarifying, François. Updated the ticket subject to reflect this.
- Subject changed from Rudder ignores the rudder.batch.reportscleaner.archive.TTL property and defaults to 30 days to Rudder max days of archived reports retained cannot be configured from properties
- 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 
Updated by 
Updated by Anonymous 
Updated by