Project

General

Profile

Bug #8246

Node configuration cache is invalidated too often

Added by François ARMAND almost 4 years ago. Updated over 3 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.

Associated revisions

Revision ad4ac0b8 (diff)
Added by François ARMAND almost 4 years ago

Fixes #8246: Node configuration cache is invalidated too often

Revision 5da71e9a (diff)
Added by François ARMAND almost 4 years ago

Fixes #8246: Node configuration cache is invalidated too often

Revision a1e20901
Added by Vincent MEMBRÉ almost 4 years ago

Merge pull request #1088 from fanf/bug_8246/node_configuration_cache_is_invalidated_too_often

Fixes #8246: Node configuration cache is invalidated too often

Revision ecacc7d1
Added by Vincent MEMBRÉ almost 4 years ago

Merge pull request #1088 from fanf/bug_8246/node_configuration_cache_is_invalidated_too_often

Fixes #8246: Node configuration cache is invalidated too often

History

#1

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

Updated by François ARMAND almost 4 years ago

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

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

Also available in: Atom PDF