Project

General

Profile

Bug #9822

Job is not run for Technique JobScheduler in Rudder

Added by Nicolas CHARLES over 1 year ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Category:
Techniques
Target version:
Target version (plugin):
Severity:
User visibility:
Effort required:
Priority:

Description

In Rudder 4.0 (and maybe 3.2?), technique Job Scheduler doesn't report anything
Outputs are:

ue@@2016-12-19 18:10:28+00:00##root@#The command will be run at a random time after 19:00 on this node (/bin/true)
cf_orchestrateur_4_labo_normation_com__1482171324_Mon_Dec_19_19_15_24_2016_0x7fb752585700:R: @@jobScheduler@@log_info@@32377fd7-02fd-43d0-aab7-28460a91347b@@fd0e6502-c9d9-41ec-a386-f025c1aae1a7@@0@@Job@@/bin/true@@2016-12-19 18:15:27+00:00##root@#The command will be run at a random time after 19:00 on this node (/bin/true)
cf_orchestrateur_4_labo_normation_com__1482171624_Mon_Dec_19_19_20_24_2016_0x7fb752585700:R: @@jobScheduler@@log_info@@32377fd7-02fd-43d0-aab7-28460a91347b@@fd0e6502-c9d9-41ec-a386-f025c1aae1a7@@0@@Job@@/bin/true@@2016-12-19 18:20:27+00:00##root@#Job has been launched (/bin/true), result will be reported on next run
cf_orchestrateur_4_labo_normation_com__1482171624_Mon_Dec_19_19_20_24_2016_0x7fb752585700:R: @@jobScheduler@@log_info@@32377fd7-02fd-43d0-aab7-28460a91347b@@fd0e6502-c9d9-41ec-a386-f025c1aae1a7@@0@@Job@@/bin/true@@2016-12-19 18:20:27+00:00##root@#The command will be run at a random time after 19:00 on this node (/bin/true)

So job was not run, and not reports afterwards


Add

Subtasks


Add

Related issues

Associated revisions

Revision 65533817 (diff)
Added by Nicolas CHARLES over 1 year ago

Fixes #9822: Job is not run for Technique JobScheduler in Rudder

History

#1 Updated by Nicolas CHARLES over 1 year ago

running manually the agent at the time of the run (or forcing with with "any") correctly defines the persistent class, and trigger the reports for subsequent runs

#2 Updated by Nicolas CHARLES over 1 year ago

"interestingly", we don't have prefixes for class names defined by job scheduler, which open door for all possible collisions :(

#3 Updated by Nicolas CHARLES over 1 year ago

  • Subject changed from No reports for Technique JobScheudler in Rudder 4.0 to No reports for Technique JobScheudler in Rudder
  • Target version changed from 3.2.11 to 3.1.18

ok, after more analysis, it fails because class test_jours_list_iterator is defined at pass3, so the report is made before the command is run, defining the persistent class job_scheduler_lock_${iterator}, and preventing the command from being executed

#4 Updated by Nicolas CHARLES over 1 year ago

  • Subject changed from No reports for Technique JobScheudler in Rudder to Job is not run for Technique JobScheduler in Rudder
  • Description updated (diff)
  • Assignee set to Nicolas CHARLES

#5 Updated by Nicolas CHARLES over 1 year ago

  • Status changed from New to In progress

#6 Updated by Nicolas CHARLES over 1 year 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/1096

#7 Updated by Nicolas CHARLES over 1 year ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

#8 Updated by Vincent MEMBRÉ over 1 year ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.18, 3.2.11, 4.0.3 and 4.1.0~beta3 which were released today.

Also available in: Atom PDF