Bug #18330
closed
Agent run frequency must not be configurable on policy servers
Added by Alexis Mousset about 4 years ago.
Updated almost 4 years ago.
Category:
Web - Config management
Description
The value is hardcoded but stays configurable in the interface, it should not!
The global settings should also specify that the setting does not apply to policy servers.
- Related to User story #3679: Make the agent run schedule configurable from 5 minutes to 6 hours, with configurable offset and splay time added
- Target version changed from 6.1.6 to 6.1.7
- Status changed from New to In progress
- Assignee set to Elaad FURREEDAN
- Status changed from In progress to Pending technical review
- Assignee changed from Elaad FURREEDAN to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/3433
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.7 which was released today.
Also available in: Atom
PDF