Actions
Bug #25652
closedDefault settings for new nodes are not applied on a accepted node
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Server components
Target version:
Pull Request:
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.
Updated by Elaad FURREEDAN 2 months ago
- Status changed from New to In progress
- Assignee set to Elaad FURREEDAN
Updated by Elaad FURREEDAN 2 months ago
Work in progess here: https://github.com/ElaadF/rudder/commit/39da5b56894bb1f879d749729495ad04c0e53a4c
Updated by Elaad FURREEDAN 2 months ago
Work in progess here: https://github.com/ElaadF/rudder/commit/c663c9b1bc6730b5ec7b6b1e8b3728e80a15566c
Updated by François ARMAND 2 months ago
- Priority changed from To review to 1 (highest)
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
Updated by Anonymous about 1 month ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|5aaf7e4a7ca17e701dc195b5e76265bc804473d5.
Updated by Alexis Mousset about 1 month ago
- Fix check changed from To do to Checked
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