Bug #18203: Missing report with directive Scheduled Job - Rudder - Issue Tracker

Custom queries

Bugs triage
Issue triage (recent)
My TR
Need technical review
Open bugs (all)
Open bugs (UI - UX)
Open bugs 7.2.0
Open UX defects (all)
Opened by users

Actions

Copy link

Bug #18203

open

Missing report with directive Scheduled Job

Added by P C over 2 years ago. Updated 4 months ago.

Status:

New

Priority:

N/A

Assignee:

Category:

Techniques

Target version:

old 6.1 issues to relocate

Pull Request:

Severity:

Minor - inconvenience | misleading | easy workaround

UX impact:

User visibility:

Operational - other Techniques | Rudder settings | Plugins

Effort required:

Priority:

Regression:

Description

I have
A general setup period of 6hours with 5hours max delay.
and
a scheduled job directive configured liked this (for all my 20 nodes):
Lowest time the command should be run at 1
Highest time the command should be run at 4
Consider the job failed after (minutes) 120
Return codes considered as a success 0
Return codes considered as a repair 1
Return codes considered as an error 2

Regularly, some nodes (not the same ones, most of the time only 1, but can be more) have a compliance message 'missing report'

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #18732: backport fix on background command execution on agent

Released

Alexis Mousset

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by P C over 2 years ago

Subject changed from Missing report with directive Scheduled Job when Opening time shorter then period to Missing report with directive Scheduled Job
Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround

I have
A general setup period of 2 hours with 1 hour max delay.
and
2 scheduled job directive configured liked this (for all my 20 nodes):
Job1
Lowest time the command should be run at 1
Highest time the command should be run at 4
Consider the job failed after (minutes) 240
Return codes considered as a success 0
Return codes considered as a repair 1
Return codes considered as an error 2
Job2
Lowest time the command should be run at 0
Highest time the command should be run at 23
Consider the job failed after (minutes) 240
Return codes considered as a success 0
Return codes considered as a repair 1
Return codes considered as an error 2

Regularly, some nodes (not the same ones, most of the time only 1, but can be more) have a compliance message 'missing report', sometime for one job, sometime for both.

Actions

Copy link

Updated by Nicolas CHARLES over 2 years ago

Some more details:
On a node, with agent schedule every 2 hours, command was executed

2020-09-30T00:50:10+00:00
2020-10-01T00:50:33+00:00
2020-10-02T00:50:03+00:00
2020-10-03T00:51:06+00:00
2020-10-05T00:50:29+00:00

so no run on the 4th and 6th (validated by file touched at beginning of action)

When a job scheduler run was expected, log only says

2020-10-05T00:07:54+00:00 R: @@jobScheduler@@log_info@@xxxxxxxxx-xxxxxxxx@@yyyy-yyyyy@@0@@None@@job_to_run_zzzz_zzzzz@@2020-10-05 00:07:46+00:00##nodeId@#Scheduling job1_to_run_zzzz_zzzzz was correct
2020-10-05T00:07:54+00:00 R: @@jobScheduler@@log_info@@xxxxxxxxx-xxxxxxxx@@yyyy-yyyyy@@0@@None@@job_to_run_zzzz_zzzzz@@2020-10-05 00:07:46+00:00##nodeId@#Scheduling Scheduling job2_to_run_zzzz_zzzzz was correct
2020-10-05T00:07:54+00:00 R: @@jobScheduler@@log_info@@xxxxxxxxx-xxxxxxxx@@yyyy-yyyyy@@0@@Job@@command1@@2020-10-05 00:07:46+00:00##nodeId@#The command will be run at a random time after 00:00 on this node
2020-10-05T00:07:54+00:00 R: @@jobScheduler@@log_info@@xxxxxxxxx-xxxxxxxx@@yyyy-yyyyy@@0@@Job@@command2@@2020-10-05 00:07:46+00:00##nodeId@#The command will be run at a random time after 00:00 on this node

There are 2 jobs, it might be related

Actions

Copy link