Project

General

Profile

Actions

Bug #18846

closed

Agent run schedule problem

Added by Lars Koenen 4 months ago. Updated about 2 months ago.

Status:
Released
Priority:
N/A
Category:
Agent
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
51

Description

I have found a problem with the agent run schedule.
When I set the schedule in the WebUI to:

  • Run agent every: 1 Hour
  • First run time: 0 Hours, 50 Minutes
  • Maximum delay: 0 Hours, 0 Minutes

the agent is still only executed on the hour.

Is my assumption correct that these settings are located on the client in the file /var/rudder/cfengine-community/inputs/rudder.json?
If so, then I have probably already found part of the error.
With the above settings, the file contains:

"AGENT_RUN_INTERVAL":"60",
"AGENT_RUN_SCHEDULE":"\"Hr00.Min00\", \"Hr01.Min00\", \"Hr02.Min00\", \"Hr03.Min00\", \"Hr04.Min00\", \"Hr05.Min00\", \"Hr06.Min00\",
  \"Hr07.Min00\", \"Hr08.Min00\", \"Hr09.Min00\", \"Hr10.Min00\", \"Hr11.Min00\", \"Hr12.Min00\",
  \"Hr13.Min00\", \"Hr14.Min00\", \"Hr15.Min00\", \"Hr16.Min00\", \"Hr17.Min00\", \"Hr18.Min00\",
  \"Hr19.Min00\", \"Hr20.Min00\", \"Hr21.Min00\", \"Hr22.Min00\", \"Hr23.Min00\"",
"AGENT_RUN_SPLAYTIME":"0",

where you can see that the minutes setting seems to have been ignored.


Subtasks 1 (0 open1 closed)

Bug #18882: Build broken by automatic upmerge of parent ticketReleasedVincent MEMBRÉActions
Actions #1

Updated by Lars Koenen 4 months ago

  • Subject changed from Agent run schedule to Agent run schedule problem
Actions #2

Updated by Lars Koenen 4 months ago

I narrowed it down further. The problem only occurs for the global setting. If I tick the checkbox "override global value" for a node, then the configured minutes are also taken into account in the scheduling of this node.

Actions #3

Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 6.2.2 to 6.2.3
Actions #4

Updated by François ARMAND 3 months ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #5

Updated by François ARMAND 3 months ago

  • Target version changed from 6.2.3 to 6.1.10
  • User visibility changed from Getting started - demo | first install | Technique editor and level 1 Techniques to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 70 to 52
Actions #6

Updated by François ARMAND 3 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/3496
Actions #7

Updated by François ARMAND 3 months ago

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

Updated by Vincent MEMBRÉ about 2 months ago

  • Status changed from Pending release to Released
  • Priority changed from 52 to 51

This bug has been fixed in Rudder 6.1.10 and 6.2.3 which were released today.

Actions

Also available in: Atom PDF