Project

General

Profile

Actions
Copy link

Bug #2454

closed

(ex PT/ Technique)JobScheduler with several Jobs returns Success but doesn't execute any other job that the first one defined.

Added by Nicolas PERRON over 12 years ago. Updated over 12 years ago.

Status:
Released
Priority:
2
Assignee:
Matthieu CERDA
Category:
Techniques
Target version:
2.3.7
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I've defined a Policy Instance (Directive for Rudder 2.4+) jobScheduler in Rudder 2.3 on Debian with two jobs: The first one must be exectued between 10AM and 111AM and the second one between 11AM and 12PM .

Until the first job is executed, the report is Unkown, after its execution, report is Success and the second one is never executed.

Here is the syslog on agent side: The first job have to execute scriptOne.sh and the second one scriptTwo.sh but there is no mention about scriptTwo.

[...]
Apr 19 10:51:26 debian-5-32 rudder[25509]:  R: @@jobScheduler@@log_info@@342369e4-f7d3-4089-8988-03cdb99ea076@@6097abb3-dd0a-4df8-b92a-7e329a021ec4@@2@@jobScheduler@@None@@2012-04-19 10:51:20+02:00##0876521e-3c81-4775-85c7-5dd7f9d5d3da@#The command will be run at a random time after 10:00 on this node (/root/scriptOne.sh)
Apr 19 10:53:01 debian-5-32 rudder[25517]:  R: @@jobScheduler@@result_success@@342369e4-f7d3-4089-8988-03cdb99ea076@@6097abb3-dd0a-4df8-b92a-7e329a021ec4@@2@@jobScheduler@@None@@2012-04-19 10:52:57+02:00##0876521e-3c81-4775-85c7-5dd7f9d5d3da@#Job return a success return code on last completed execution (/root/scriptOne.sh)
Apr 19 10:53:01 debian-5-32 rudder[25569]:  R: @@jobScheduler@@log_info@@342369e4-f7d3-4089-8988-03cdb99ea076@@6097abb3-dd0a-4df8-b92a-7e329a021ec4@@2@@jobScheduler@@None@@2012-04-19 10:52:57+02:00##0876521e-3c81-4775-85c7-5dd7f9d5d3da@#Job has been launched (/root/scriptOne.sh), result will be reported on next run
Apr 19 10:53:01 debian-5-32 rudder[25569]:  R: @@jobScheduler@@log_info@@342369e4-f7d3-4089-8988-03cdb99ea076@@6097abb3-dd0a-4df8-b92a-7e329a021ec4@@2@@jobScheduler@@None@@2012-04-19 10:52:57+02:00##0876521e-3c81-4775-85c7-5dd7f9d5d3da@#The command will be run at a random time after 10:00 on this node (/root/scriptOne.sh)
Apr 19 10:56:14 debian-5-32 rudder[25848]:  R: @@jobScheduler@@result_success@@342369e4-f7d3-4089-8988-03cdb99ea076@@6097abb3-dd0a-4df8-b92a-7e329a021ec4@@2@@jobScheduler@@None@@2012-04-19 10:56:07+02:00##0876521e-3c81-4775-85c7-5dd7f9d5d3da@#Job return a success return code on last completed execution (/root/scriptOne.sh)
[...]
Apr 19 11:01:19 debian-5-32 rudder[26229]:  R: @@jobScheduler@@result_success@@342369e4-f7d3-4089-8988-03cdb99ea076@@6097abb3-dd0a-4df8-b92a-7e329a021ec4@@2@@jobScheduler@@None@@2012-04-19 11:01:05+02:00##0876521e-3c81-4775-85c7-5dd7f9d5d3da@#Job return a success return code on last completed execution (/root/scriptOne.sh)
Apr 19 11:01:19 debian-5-32 rudder[26229]:  R: @@jobScheduler@@log_info@@342369e4-f7d3-4089-8988-03cdb99ea076@@6097abb3-dd0a-4df8-b92a-7e329a021ec4@@2@@jobScheduler@@None@@2012-04-19 
[...]
Apr 19 11:46:29 debian-5-32 rudder[29210]:  R: @@jobScheduler@@log_info@@342369e4-f7d3-4089-8988-03cdb99ea076@@6097abb3-dd0a-4df8-b92a-7e329a021ec4@@2@@jobScheduler@@None@@2012-04-19 11:46:11+02:00##0876521e-3c81-4775-85c7-5dd7f9d5d3da@#The command will be run at a random time after 10:00 on this node (/root/scriptOne.sh)
Apr 19 11:52:19 debian-5-32 rudder[29535]:  R: @@jobScheduler@@result_success@@342369e4-f7d3-4089-8988-03cdb99ea076@@6097abb3-dd0a-4df8-b92a-7e329a021ec4@@2@@jobScheduler@@None@@2012-04-19 11:51:27+02:00##0876521e-3c81-4775-85c7-5dd7f9d5d3da@#Job return a success return code on last completed execution (/root/scriptOne.sh)
Apr 19 11:52:19 debian-5-32 rudder[29535]:  R: @@jobScheduler@@log_info@@342369e4-f7d3-4089-8988-03cdb99ea076@@6097abb3-dd0a-4df8-b92a-7e329a021ec4@@2@@jobScheduler@@None@@2012-04-19 11:51:27+02:00##0876521e-3c81-4775-85c7-5dd7f9d5d3da@#The command will be run at a random time after 10:00 on this node (/root/scriptOne.sh)
Apr 19 11:56:29 debian-5-32 rudder[29868]:  R: @@jobScheduler@@result_success@@342369e4-f7d3-4089-8988-03cdb99ea076@@6097abb3-dd0a-4df8-b92a-7e329a021ec4@@2@@jobScheduler@@None@@2012-04-19 11:56:13+02:00##0876521e-3c81-4775-85c7-5dd7f9d5d3da@#Job return a success return code on last completed execution (/root/scriptOne.sh)
Apr 19 11:56:31 debian-5-32 rudder[29868]:  R: @@jobScheduler@@log_info@@342369e4-f7d3-4089-8988-03cdb99ea076@@6097abb3-dd0a-4df8-b92a-7e329a021ec4@@2@@jobScheduler@@None@@2012-04-19 11:56:13+02:00##0876521e-3c81-4775-85c7-5dd7f9d5d3da@#The command will be run at a random time after 10:00 on this node (/root/scriptOne.sh)
Apr 19 12:02:10 debian-5-32 rudder[30197]:  R: @@jobScheduler@@result_success@@342369e4-f7d3-4089-8988-03cdb99ea076@@6097abb3-dd0a-4df8-b92a-7e329a021ec4@@2@@jobScheduler@@None@@2012-04-19 12:01:59+02:00##0876521e-3c81-4775-85c7-5dd7f9d5d3da@#Job return a success return code on last completed execution (/root/scriptOne.sh)
Apr 19 12:02:11 debian-5-32 rudder[30197]:  R: @@jobScheduler@@log_info@@342369e4-f7d3-4089-8988-03cdb99ea076@@6097abb3-dd0a-4df8-b92a-7e329a021ec4@@2@@jobScheduler@@None@@2012-04-19 12:01:59+02:00##0876521e-3c81-4775-85c7-5dd7f9d5d3da@#The command will be run at a random time after 10:00 on this node (/root/scriptOne.sh)
[...]

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #2485: (ex PT/ Technique)JobScheduler: When several jobs are defined, even if "success" is reported by the node, Rudder consider it as "Error"ReleasedJonathan CLARKE2012-05-09Actions
Actions
Copy link
 #1

Updated by Nicolas PERRON over 12 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Nicolas PERRON over 12 years ago

  • Target version changed from 2.3.7 to 2.3.8
Actions
Copy link
 #3

Updated by Jonathan CLARKE over 12 years ago

  • Assignee changed from Jonathan CLARKE to Matthieu CERDA
Actions
Copy link
 #4

Updated by Jonathan CLARKE over 12 years ago

Matthieu tells me that this bug is due to the PT not being "multi instance".

Actions
Copy link
 #5

Updated by Matthieu CERDA over 12 years ago

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

Applied in changeset commit:e4f0c0217eed1a88417148ccd75db8e4d7855237.

Actions
Copy link
 #6

Updated by Nicolas PERRON over 12 years ago

Seems good to me

Actions
Copy link
 #7

Updated by Nicolas PERRON over 12 years ago

  • Target version changed from 2.3.8 to 2.3.7

It has been fixed in 2.3.7

Actions
Copy link
 #8

Updated by Jonathan CLARKE over 12 years ago

  • Status changed from Pending technical review to Released

Nicolas PERRON wrote:

Seems good to me

Actually, I disagree slightly: the component name ("Job" in policy.xml) is not used in the reports in job_scheduler.st, so reporting will fail. But this has already been identified in #2485, so closing this one and fixing #2485.

Actions
Copy link

Also available in: Atom PDF