Project

General

Profile

Actions

Bug #9320

closed

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

Added by François ARMAND over 4 years ago. Updated over 4 years ago.

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

Actions #1

Updated by François ARMAND over 4 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
Actions #2

Updated by François ARMAND over 4 years ago

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

Updated by Vincent MEMBRÉ over 4 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.

Actions

Also available in: Atom PDF