Project

General

Profile

Actions
Copy link

Bug #6038

closed

Wrong reporting after execution of migration script to change the way reports are used from the database

Added by Nicolas CHARLES about 10 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - Compliance & node report
Target version:
3.0.0~rc1
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

in #6005, we changed the way we handle the reporting, by taking the most recent one (insertion wise) from the database.
however, we left a lot of entry to null; which is not good because when we sort, NULL is always before the others (DESC or ASC wise)
We need to have a default value to 0 to correct this

Note: the problems corrects itself after a while, when old reports are deleted from the database

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #6005: If a node had a date in the future, but returned to current time, the reporting will always be invalid (until it catches up with the future date)ReleasedNicolas CHARLES2014-12-16Actions
Actions
Copy link
 #1

Updated by Nicolas CHARLES about 10 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/740
Actions
Copy link
 #2

Updated by Nicolas CHARLES almost 10 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É almost 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.0~rc1, which was released today.

Actions
Copy link

Also available in: Atom PDF