Bug #23956
closedRudder agent scheduled runs are not triggered at regular interval
Description
The agent uses the ScheduledTask "RandomDelay" feature, but this is recalculated for each run, and so, the agent does not run every "AGENT_RUN_INTERVAL" but every "AGENT_RUN_INTERVAL" +- a random minutes delay between 0 and "AGENT_RUN_SPLAYTIME".
To keep the startime spray and re-enable the agent run periodicity, the best solution seem to let the webapp generates a starting hours/minutes/seconds calculated from the node uuid and the node settings which should look like:
"00:00:00" + "First run time" (taken from settings) + random(0, "Maximum delay" from setting)
The computed value should be added to the rudder.json generated in the policies for each node, under a key named "AGENT_RUN_STARTTIME" and with a value following the format: "HH:MM:SS".
Updated by François ARMAND 10 months ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND 10 months ago
- Project changed from 78 to Rudder
- Category changed from Rudder web app to Web - Config management
- Target version changed from 7.3 to 7.3.11
So in fact, this need to be changed in Rudder core.
Updated by François ARMAND 10 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Clark ANDRIANASOLO
- Pull Request set to https://github.com/Normation/rudder/pull/5304
Updated by Anonymous 10 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|db51aadc417acf357870b1f253bc7afd5bc8177c.
Updated by François ARMAND 10 months ago
- Fix check changed from To do to Checked
Checked with sub issue
Updated by Vincent MEMBRÉ 9 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.3.11 which was released today.