Actions
Bug #4841
closedJob Scheduler Technique should not use ifelapsed to avoid running several time same job
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
Since in #4769 we are going to remove cf_lock.tcdb files, we need to make sure that we don't use ifelapsed to avoid running several time the same job (if we run manually the agent after killing the lock base, in the right ( minutes interval)
There is nearly no impact, as the probability of this hitting a user is nearly null (have to run manually the agent, in the right interval, right after a moment where lock is killed)
Updated by Nicolas CHARLES over 10 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/362
Updated by Nicolas CHARLES over 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:36a7c3bc16d7d7ed9818256a31451d147dc573db.
Updated by Nicolas CHARLES over 10 years ago
Applied in changeset policy-templates:commit:4c721ba20758b85aaeb6b46546208492155b6434.
Updated by Vincent MEMBRÉ over 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.9.5 (announcement , changelog) and 2.10.1 (announcement , changelog), which were released today.
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions