Project

General

Profile

Bug #4840

"Job Scheduler" Technique miss runs when using a non-default agent execution frequency

Added by Nicolas CHARLES about 5 years ago. Updated 6 months ago.

Status:
Released
Priority:
2
Category:
Techniques
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Priority:
0

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


Subtasks

ncf - User story #13984: Add a bundle to define persistent classes for job scheduler techniquesReleasedAlexis MOUSSETActions

Related issues

Has duplicate Rudder - Bug #5535: jobscheduler technique doesn't run jobs if agent interval in 60mnRejected2014-09-16Actions

Associated revisions

Revision 52e47778 (diff)
Added by Nicolas CHARLES 8 months ago

Refs #4840: Creation of jobScheduler version 3.0 from 2.0

Revision aa1ce5ba (diff)
Added by Nicolas CHARLES 7 months ago

Fixes #4840: Job Scheduler Technique will miss some jobs when using a non-default agent execution frequency

History

#1

Updated by Nicolas CHARLES about 5 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
#2

Updated by Nicolas CHARLES about 5 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 :/

#3

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 2.10.1 to 2.10.2
#4

Updated by Jonathan CLARKE about 5 years ago

  • Target version changed from 2.10.2 to 2.10.3
#5

Updated by Jonathan CLARKE about 5 years ago

  • Target version changed from 2.10.3 to 2.10.4
#6

Updated by Nicolas PERRON almost 5 years ago

  • Target version changed from 2.10.4 to 2.6.18
#7

Updated by Nicolas PERRON almost 5 years ago

  • Target version changed from 2.6.18 to 2.10.5
#8

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 2.10.5 to 2.10.6
#9

Updated by Matthieu CERDA almost 5 years ago

  • Target version changed from 2.10.6 to 2.10.7
#10

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.10.7 to 2.10.8
#11

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.10.8 to 2.10.9
#12

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.10.9 to 2.10.10
#13

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.10.10 to 2.10.11
#14

Updated by François ARMAND over 4 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 ?")

#15

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.10.11 to 2.10.12
#16

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.10.12 to 2.10.13
#17

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.10.13 to 2.10.14
#18

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 2.10.14 to 2.10.15
#19

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 2.10.15 to 2.10.16
#20

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 2.10.16 to 2.10.17
#21

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 2.10.17 to 2.10.18
#22

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 2.10.18 to 2.10.19
#23

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.10.19 to 2.10.20
#24

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.10.20 to 277
#25

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 277 to 2.11.18
#26

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.18 to 2.11.19
#27

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.19 to 2.11.20
#28

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 2.11.20 to 2.11.21
#29

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 2.11.21 to 2.11.22
#30

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 2.11.22 to 2.11.23
#31

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.11.23 to 2.11.24
#32

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 2.11.24 to 308
#33

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 308 to 3.1.14
#34

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 3.1.14 to 3.1.15
#35

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 3.1.15 to 3.1.16
#36

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 3.1.16 to 3.1.17
#37

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 3.1.17 to 3.1.18
#38

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 3.1.18 to 3.1.19
#39

Updated by François ARMAND over 2 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
#40

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 3.1.19 to 3.1.20
#41

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.20 to 3.1.21
#42

Updated by François ARMAND about 2 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
#43

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 3.1.21 to 3.1.22
#44

Updated by Benoît PECCATTE about 2 years ago

  • Priority changed from 30 to 31
#45

Updated by Benoît PECCATTE about 2 years ago

  • Priority changed from 31 to 44
#46

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.22 to 3.1.23
#47

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.1.23 to 3.1.24
  • Priority changed from 44 to 45
#48

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.24 to 3.1.25
#49

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.1.25 to 387
  • Priority changed from 45 to 46
#50

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 387 to 4.1.10
#51

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.1.10 to 4.1.11
  • Priority changed from 46 to 47
#52

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 4.1.11 to 4.1.12
#53

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 4.1.12 to 4.1.13
  • Priority changed from 47 to 48
#54

Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 4.1.13 to 4.1.14
#55

Updated by Benoît PECCATTE 12 months ago

  • Target version changed from 4.1.14 to 4.1.15
  • Priority changed from 48 to 49
#56

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 4.1.15 to 4.1.16
#57

Updated by Vincent MEMBRÉ 9 months ago

  • Target version changed from 4.1.16 to 4.1.17
  • Priority changed from 49 to 50
#58

Updated by Nicolas CHARLES 8 months ago

  • Target version changed from 4.1.17 to 4.3.7
  • Priority changed from 50 to 0
#59

Updated by Nicolas CHARLES 8 months ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
#60

Updated by Nicolas CHARLES 8 months 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
#61

Updated by Vincent MEMBRÉ 8 months ago

  • Target version changed from 4.3.7 to 4.3.8
#62

Updated by Nicolas CHARLES 7 months ago

  • Status changed from Pending technical review to Pending release
#63

Updated by Vincent MEMBRÉ 6 months 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
#64

Updated by Vincent MEMBRÉ 6 months ago

  • Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.8 and 5.0.4 which were released today.
Changelog
Changelog

Also available in: Atom PDF