Actions
Bug #9320
closed
Rule & directive order is not taken into account for nodeConfig cache invalidation
Status:
Released
Priority:
2
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
We have a node configuration cache that tracks if a node config should be updated or not.
In that cache, we don't track the ordering (rule name & directive name). That means that if we only changed that, the config won't be updated, resulting to no policies written for the node.
Updated by François ARMAND about 8 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/1258
Updated by François ARMAND about 8 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|345d4b1b7b07b07c362ed1df460d7b12d1b0fbbb.
Updated by Vincent MEMBRÉ about 8 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.2.9 and 3.1.16 which were released today.
- 3.2.9: Announce Changelog
- 3.1.16: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions