Project

General

Profile

Actions

Bug #25652

closed

Default settings for new nodes are not applied on a accepted node

Added by Elaad FURREEDAN 2 months ago. Updated about 1 month ago.

Status:
Released
Priority:
1 (highest)
Category:
Server components
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I hate Rudder for that
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Medium
Priority:
139
Name check:
To do
Fix check:
Checked
Regression:
Yes

Description

In Administration -> Settings -> Default settings for new nodes
if we modify this setting (the node state or the policy mode), the setting is modified and saved, but on the node side, when we accept the node, this setting is not taken into account.

Actions #1

Updated by Elaad FURREEDAN 2 months ago

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

Updated by François ARMAND 2 months ago

  • Priority changed from N/A to To review
Actions #5

Updated by François ARMAND 2 months ago

  • Priority changed from To review to 1 (highest)
Actions #6

Updated by Elaad FURREEDAN about 2 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Elaad FURREEDAN to Clark ANDRIANASOLO
  • Pull Request set to https://github.com/Normation/rudder/pull/5949
Actions #7

Updated by Anonymous about 1 month ago

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

Updated by Alexis Mousset about 1 month ago

  • Fix check changed from To do to Checked
Actions #10

Updated by Vincent MEMBRÉ about 1 month ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 8.1.8 and 8.2.1 which were released today.

Actions

Also available in: Atom PDF