Project

General

Profile

Actions

Bug #4840

closed

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

Added by Nicolas CHARLES almost 7 years ago. Updated over 2 years 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 1 (0 open1 closed)

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
Actions #1

Updated by Nicolas CHARLES almost 7 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
Actions #2

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

Actions #3

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 2.10.1 to 2.10.2
Actions #4

Updated by Jonathan CLARKE almost 7 years ago

  • Target version changed from 2.10.2 to 2.10.3
Actions #5

Updated by Jonathan CLARKE almost 7 years ago

  • Target version changed from 2.10.3 to 2.10.4
Actions #6

Updated by Nicolas PERRON over 6 years ago

  • Target version changed from 2.10.4 to 2.6.18
Actions #7

Updated by Nicolas PERRON over 6 years ago

  • Target version changed from 2.6.18 to 2.10.5
Actions #8

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 2.10.5 to 2.10.6
Actions #9

Updated by Matthieu CERDA over 6 years ago

  • Target version changed from 2.10.6 to 2.10.7
Actions #10

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 2.10.7 to 2.10.8
Actions #11

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 2.10.8 to 2.10.9
Actions #12

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 2.10.9 to 2.10.10
Actions #13

Updated by Vincent MEMBRÉ over 6 years ago

  • Target version changed from 2.10.10 to 2.10.11
Actions #14

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

Actions #15

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 2.10.11 to 2.10.12
Actions #16

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 2.10.12 to 2.10.13
Actions #17

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 2.10.13 to 2.10.14
Actions #18

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 2.10.14 to 2.10.15
Actions #19

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 2.10.15 to 2.10.16
Actions #20

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.10.16 to 2.10.17
Actions #21

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.10.17 to 2.10.18
Actions #22

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.10.18 to 2.10.19
Actions #23

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.10.19 to 2.10.20
Actions #24

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.10.20 to 277
Actions #25

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 277 to 2.11.18
Actions #26

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions #27

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions #28

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions #29

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions #30

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions #31

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions #32

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 2.11.24 to 308
Actions #33

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 308 to 3.1.14
Actions #34

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #35

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #36

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #37

Updated by Vincent MEMBRÉ over 4 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #38

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #39

Updated by François ARMAND about 4 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
Actions #40

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #41

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #42

Updated by François ARMAND almost 4 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
Actions #43

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #44

Updated by Benoît PECCATTE almost 4 years ago

  • Priority changed from 30 to 31
Actions #45

Updated by Benoît PECCATTE almost 4 years ago

  • Priority changed from 31 to 44
Actions #46

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions #47

Updated by Vincent MEMBRÉ over 3 years ago

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

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #49

Updated by Vincent MEMBRÉ over 3 years ago

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

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 387 to 4.1.10
Actions #51

Updated by Vincent MEMBRÉ about 3 years ago

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

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 4.1.11 to 4.1.12
Actions #53

Updated by Vincent MEMBRÉ almost 3 years ago

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

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 4.1.13 to 4.1.14
Actions #55

Updated by Benoît PECCATTE almost 3 years ago

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

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.1.15 to 4.1.16
Actions #57

Updated by Vincent MEMBRÉ over 2 years ago

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

Updated by Nicolas CHARLES over 2 years ago

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

Updated by Nicolas CHARLES over 2 years ago

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

Updated by Nicolas CHARLES over 2 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
Actions #61

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 4.3.7 to 4.3.8
Actions #62

Updated by Nicolas CHARLES over 2 years ago

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

Updated by Vincent MEMBRÉ over 2 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
Actions #64

Updated by Vincent MEMBRÉ over 2 years 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
Actions

Also available in: Atom PDF