Project

General

Profile

Actions
Copy link

Bug #7080

closed

Clear cache doesn't regenerate expected reports

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

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - Config management
Target version:
2.11.13
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

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 1 (0 open — 1 closed)

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
Actions
Copy link
 #1

Updated by Nicolas CHARLES over 9 years ago

  • Target version set to 2.11.13

this happens in 2.11 also

Actions
Copy link
 #2

Updated by Nicolas CHARLES over 9 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
Actions
Copy link
 #3

Updated by Nicolas CHARLES over 9 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
Actions
Copy link
 #4

Updated by Nicolas CHARLES over 9 years ago

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

Updated by François ARMAND over 9 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.

Actions
Copy link

Also available in: Atom PDF