Project

General

Profile

Actions

Bug #6038

closed

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

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

Status:
Released
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Severity:
User visibility:
Effort required:
Priority:

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

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 #1

Updated by Nicolas CHARLES over 6 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 #2

Updated by Nicolas CHARLES over 6 years ago

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

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

Also available in: Atom PDF