Project

General

Profile

Bug #9320

Rule & directive order is not taken into account for nodeConfig cache invalidation

Added by François ARMAND about 1 year ago. Updated about 1 year ago.

Status:
Released
Priority:
2
Category:
Web - Config management
Target version:
Target version (plugin):
Severity:
User visibility:
Effort required:
Priority:

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.

Associated revisions

Revision 345d4b1b
Added by François ARMAND about 1 year ago

Fixes #9320: Rule & directive order is not taken into account for nodeConfig cache invalidation

Revision 86b5e112
Added by François ARMAND about 1 year ago

Merge pull request #1258 from fanf/bug_9320/rule_directive_order_is_not_taken_into_account_for_nodeconfig_cache_invalidation

Fixes #9320: Rule & directive order is not taken into account for nodeConfig cache invalidation

History

#1 Updated by François ARMAND about 1 year 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

#2 Updated by François ARMAND about 1 year ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

#3 Updated by Vincent MEMBRÉ about 1 year 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.

Also available in: Atom PDF