Bug #4840
closed"Job Scheduler" Technique miss runs when using a non-default agent execution frequency
Added by Nicolas CHARLES over 10 years ago. Updated about 2 years ago.
Description
If we use a non standard agent execution frequency (more than 5 minutes), the job sheduler technique may not run jobs, as the splayclass(hourly) is only defined on a 5 minutes interval
Updated by Nicolas CHARLES about 10 years ago
- Subject changed from Job Scheduler Technique may not execute jobs if using a non-default agent execution frequency to Job Scheduler Technique will miss some jobs when using a non-default agent execution frequency
Updated by Nicolas CHARLES about 10 years ago
I honestly have NO IDEA on how to fix this. If the agent execution is not often engouh (6h interval for agent execution against a 2h time schedule) it will completly miss the schedule :/
Updated by Vincent MEMBRÉ about 10 years ago
- Target version changed from 2.10.1 to 2.10.2
Updated by Jonathan CLARKE about 10 years ago
- Target version changed from 2.10.2 to 2.10.3
Updated by Jonathan CLARKE about 10 years ago
- Target version changed from 2.10.3 to 2.10.4
Updated by Nicolas PERRON about 10 years ago
- Target version changed from 2.10.4 to 2.6.18
Updated by Nicolas PERRON about 10 years ago
- Target version changed from 2.6.18 to 2.10.5
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.10.5 to 2.10.6
Updated by Matthieu CERDA almost 10 years ago
- Target version changed from 2.10.6 to 2.10.7
Updated by Vincent MEMBRÉ almost 10 years ago
- Target version changed from 2.10.7 to 2.10.8
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.8 to 2.10.9
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.9 to 2.10.10
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.10 to 2.10.11
Updated by François ARMAND over 9 years ago
Is there anything in CFEngine 3.6 that could help refactor that (quite hard) technique in a simpler way - and allows to remove that issue ?
There is also the question of the semantic we want to have for the missing runs: do we run them as soon as we saw that one is missing, or do we way for the next interval ? And of course, the second option must not lead to a "never run the job" if we are in the case matching the current issue (i.e, we have to be able to decide between "as close as we could have been for the job datetime - so ok, say it the same instant" from "we missed a job schedule, because perhaps the machine was down, what do we do with missed jobs ?")
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.11 to 2.10.12
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.12 to 2.10.13
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.13 to 2.10.14
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.10.14 to 2.10.15
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.10.15 to 2.10.16
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.10.16 to 2.10.17
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 2.10.17 to 2.10.18
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 2.10.18 to 2.10.19
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 2.10.19 to 2.10.20
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.10.20 to 277
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 277 to 2.11.18
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.18 to 2.11.19
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.19 to 2.11.20
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.20 to 2.11.21
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 2.11.21 to 2.11.22
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 2.11.22 to 2.11.23
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 2.11.23 to 2.11.24
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 2.11.24 to 308
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 308 to 3.1.14
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.17 to 3.1.18
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.18 to 3.1.19
Updated by François ARMAND over 7 years ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Infrequent - complex configurations | third party integrations
- Priority set to 0
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.19 to 3.1.20
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.20 to 3.1.21
Updated by François ARMAND about 7 years ago
- User visibility changed from Infrequent - complex configurations | third party integrations to Operational - other Techniques | Technique editor | Rudder settings
- Priority changed from 0 to 30
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.21 to 3.1.22
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 3.1.22 to 3.1.23
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 3.1.23 to 3.1.24
- Priority changed from 44 to 45
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 3.1.24 to 3.1.25
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 3.1.25 to 387
- Priority changed from 45 to 46
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 387 to 4.1.10
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.10 to 4.1.11
- Priority changed from 46 to 47
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.11 to 4.1.12
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.12 to 4.1.13
- Priority changed from 47 to 48
Updated by Vincent MEMBRÉ about 6 years ago
- Target version changed from 4.1.13 to 4.1.14
Updated by Benoît PECCATTE about 6 years ago
- Target version changed from 4.1.14 to 4.1.15
- Priority changed from 48 to 49
Updated by Vincent MEMBRÉ almost 6 years ago
- Target version changed from 4.1.15 to 4.1.16
Updated by Vincent MEMBRÉ almost 6 years ago
- Target version changed from 4.1.16 to 4.1.17
- Priority changed from 49 to 50
Updated by Nicolas CHARLES over 5 years ago
- Target version changed from 4.1.17 to 4.3.7
- Priority changed from 50 to 0
Updated by Nicolas CHARLES over 5 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES over 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1370
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 4.3.7 to 4.3.8
Updated by Nicolas CHARLES over 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|aa1ce5ba65b71b23267002b3e8ed0efce07b72f7.
Updated by Vincent MEMBRÉ over 5 years ago
- Subject changed from Job Scheduler Technique will miss some jobs when using a non-default agent execution frequency to "Job Scheduler" Technique miss runs when using a non-default agent execution frequency
Updated by Vincent MEMBRÉ over 5 years ago
- Status changed from Pending release to Released