Project

General

Profile

Actions

Bug #8246

closed

Node configuration cache is invalidated too often

Added by François ARMAND about 5 years ago. Updated almost 5 years ago.

Status:
Released
Priority:
1
Category:
Web - Config management
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

There a bug in the current "save node configuration cache" method that delete node cache for not modified cache. So, in some case, you could hit cycle where a part of nodes are saved (removing the other part), then the other part is saved (removing the first), etc.

Of course, all forseable bad consequences happens: increased generation time, patological config id modification without actual changes in the expected reports (and yes, we get bad results with compliance), etc.

Actions #1

Updated by François ARMAND about 5 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/1088
Actions #2

Updated by François ARMAND almost 5 years ago

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

Updated by Vincent MEMBRÉ almost 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.21, 3.0.16, 3.1.10 and 3.2.3 which were released on 2016-06-01, but not announced.

Actions

Also available in: Atom PDF