Project

General

Profile

Bug #7080

Clear cache doesn't regenerate expected reports

Added by Nicolas CHARLES over 5 years ago. Updated over 5 years ago.

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

Description

Somehow, expected reports got corrupt in an install, and clear cache didn't regenerate them at all
There is something fishy there


Related issues

Related to Rudder - Bug #6519: When we add a node in a rule, we lose all compliance info on this rule applied on it, and we change promises of all the nodes of the ruleReleasedFrançois ARMAND2015-05-25Actions
#1

Updated by Nicolas CHARLES over 5 years ago

  • Target version set to 2.11.13

this happens in 2.11 also

#2

Updated by Nicolas CHARLES over 5 years ago

  • Related to Bug #6519: When we add a node in a rule, we lose all compliance info on this rule applied on it, and we change promises of all the nodes of the rule added
#3

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/910
#4

Updated by Nicolas CHARLES over 5 years ago

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

Updated by François ARMAND over 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.13, 3.0.8 and 3.1.1 which were released today.

Also available in: Atom PDF