Actions
Bug #18330
closed
Agent run frequency must not be configurable on policy servers
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
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.
Updated by François ARMAND about 4 years ago
- Related to User story #3679: Make the agent run schedule configurable from 5 minutes to 6 hours, with configurable offset and splay time added
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.6 to 6.1.7
Updated by Elaad FURREEDAN almost 4 years ago
- Status changed from New to In progress
- Assignee set to Elaad FURREEDAN
Updated by Elaad FURREEDAN almost 4 years ago
- 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
Updated by Anonymous almost 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|95124a7e1f797282f9c600fc07f30f985054fcdb.
Updated by Alexis Mousset almost 4 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ almost 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.7 which was released today.
Actions