Actions
Bug #19227
closed
setting a job with schedule_simple in catchup mode does not honor the schedule
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
When we use the "catchup" mode in schedule_* , it will run the job asap if the job was never run. And then define a persistent class for the length of the desired frequency
So when it will be the desired period for this job, the class will still be set, and the job won't be run. After the end of the persistent class, the job will be caught up
The result is a job not splayed at all
Impact is worsen by the fact that it is used by rudder inventory splay mechanism
Updated by Nicolas CHARLES over 3 years ago
- Status changed from New to In progress
Updated by Nicolas CHARLES over 3 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/ncf/pull/1291
Updated by Nicolas CHARLES over 3 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset commit:2ac34ab9239bd6eeaacb9dc5b3e762b8b531e27b.
Updated by François ARMAND over 3 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ over 3 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.13 and 6.2.7 which were released today.
Updated by Alexis Mousset over 2 years ago
- Project changed from 41 to Rudder
- Category set to Generic methods
Actions