Actions
Bug #5582
closed
Check on age of promises in failsafe doesn't take into account specific schedule, nor lmdb database, and should probably be remove
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
the failsafe checks the age of last_successful_update, and if it is older than 1 hour, remove lock database
However, it doesn't take into account the cfenigne 3.6 lock database, nor schedules which are different than 5 minutes
Since check_rudder_agent does the same thing (but better), and since it can causes crashes on Windows (error with irange), i think it should be removed
Updated by Nicolas CHARLES about 10 years ago
- Status changed from New to Pending technical review
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/512
Updated by Nicolas CHARLES about 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:a9726af37ee4eed46faeb3b8e723936f89de8542.
Updated by Jonathan CLARKE about 10 years ago
Applied in changeset policy-templates:commit:4e44d9a29d341e8c0cc9d77f9a7de59d2353e75e.
Updated by Vincent MEMBRÉ about 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.11.4, which was released today.
- Announcement
- Changelog
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions