Project

General

Profile

Actions

Bug #18330

closed

Agent run frequency must not be configurable on policy servers

Bug #18330: Agent run frequency must not be configurable on policy servers

Added by Alexis Mousset over 5 years ago. Updated about 5 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
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.


Related issues 1 (0 open1 closed)

Related to Rudder - User story #3679: Make the agent run schedule configurable from 5 minutes to 6 hours, with configurable offset and splay timeReleasedNicolas CHARLESActions

Updated by François ARMAND over 5 years ago Actions #1

  • 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É over 5 years ago Actions #2

  • Target version changed from 6.1.6 to 6.1.7

Updated by Elaad FURREEDAN about 5 years ago Actions #3

  • Status changed from New to In progress
  • Assignee set to Elaad FURREEDAN

Updated by Elaad FURREEDAN about 5 years ago Actions #4

  • 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 about 5 years ago Actions #5

  • Status changed from Pending technical review to Pending release

Updated by Alexis Mousset about 5 years ago Actions #6

  • Fix check changed from To do to Checked

Updated by Vincent MEMBRÉ about 5 years ago Actions #7

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.1.7 which was released today.

Actions

Also available in: PDF Atom