Project

General

Profile

Actions
Copy link

Bug #8364

closed

Bug #8051: Compliance is not correctly computed if we receive run agent right after generation

Only invalidate cache for node with new completed runs

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

Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas CHARLES
Category:
Web - Compliance & node report
Target version:
3.0.16
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

For now, we are updating (compliance) cache even for node with partial runs, which are not taken into account in the compliance calculus. So we are just invalidating compliance for nothing for them.

Actions
Copy link
 #1

Updated by François ARMAND over 8 years ago

  • Status changed from New to In progress
Actions
Copy link
 #2

Updated by François ARMAND over 8 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/1102
Actions
Copy link
 #3

Updated by François ARMAND over 8 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 8 years ago

  • Status changed from Pending release to Released

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

Actions
Copy link

Also available in: Atom PDF