Actions
Bug #15890
closedBug #15802: Clean up reports with log_* types more than once a day
Batch which deletes log reports displays an error when default run interval is not defined
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
When rudder starts on first boot, we get that error:
[2019-10-07 15:34:29] ERROR scheduledJob - Error when trying to get maximun run interval, defaulting to 5 minutes. Error was:
This is because default run interval is not defined in LDAP in that case (default value is used), but we don't process correctly the missing property.
Updated by François ARMAND about 5 years ago
- Related to Bug #15888: Batch which cleans log reports should not start if LDAP is unavailable added
Updated by François ARMAND about 5 years ago
- Status changed from New to In progress
Updated by François ARMAND about 5 years ago
- Related to Bug #15802: Clean up reports with log_* types more than once a day added
Updated by François ARMAND about 5 years ago
- Related to deleted (Bug #15802: Clean up reports with log_* types more than once a day)
Updated by François ARMAND about 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/2510
Updated by François ARMAND about 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|1d506e068ac58a1302b4d8451996403b4a0804af.
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.15 to 5.0.14
Updated by François ARMAND about 5 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset about 5 years ago
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.14 which was released today.
Actions