Project

General

Profile

Actions
Copy link

Architecture #20747

closed

Use a unique id to identify reports

Added by Vincent MEMBRÉ about 2 years ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - Compliance & node report
Target version:
7.1.0~beta1
Pull Request:
https://github.com/Normation/rudder/p...
Effort required:
Name check:
To do
Fix check:
To do
Regression:

Description

We use to match report by looking to their component value and their values. but this leads to various falws in our compliance computation system.

We don't match reports precisely and we have to group all reports that have the same component so we cannot be sure that the report we correctly assigned, espcially in case where we have varialbe
It does not mix well with block feature, since we cannot find out from the report in which block this report belong (if the component name is shared with others)
We can not use varialble in component name, and it something we really want to do.

Subtasks 17 (0 open — 17 closed)

Architecture #20773: Add a new logger to use properly use report_idReleasedNicolas CHARLESActions
Architecture #20806: Use the new logger v4 for service methodsReleasedFélix DALLIDETActions
Bug #20850: Some service methods don't report correctlyReleasedNicolas CHARLESActions
Architecture #20823: Broken v4 loggerReleasedNicolas CHARLESActions
Architecture #20785: Use a unique id to identify reports - ruddercReleasedVincent MEMBRÉActions
Architecture #20795: Fix relayd testsResolvedFrançois ARMANDActions
Architecture #20796: Change back group permissionsReleasedAlexis MoussetActions
Architecture #20797: Missing migration script for serial -> reportId columnReleasedAlexis MoussetActions
Architecture #20875: call migration script on update to 7.1ReleasedAlexis MoussetActions
Architecture #20876: serial needs also to me renamed in archivesysevents tableReleasedFrançois ARMANDActions
Architecture #20798: Call the migration script during rudder-upgradeRejectedActions
Bug #20804: Compliance of technique with reportid does not appear on node complianceReleasedFrançois ARMANDActions
Bug #20805: Compliance of technique with reportid does not appear on node compliance - broken v4 loggerReleasedFrançois ARMANDActions
Bug #20808: Missing reports with a reportid are missing in complianceReleasedAlexis MoussetActions
Bug #20815: Ensure variable in component name and values are OKReleasedNicolas CHARLESActions
Bug #20828: Unexpected/missing for same component, same valueReleasedNicolas CHARLESActions
User story #20851: Regroup report with their values, not with the expanded valueReleasedFrançois ARMANDActions
Actions
Copy link
 #1

Updated by Vincent MEMBRÉ about 2 years ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ about 2 years ago

  • Assignee changed from Vincent MEMBRÉ to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/4167
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ about 2 years ago

  • Status changed from In progress to Pending release
Actions
Copy link
 #4

Updated by François ARMAND about 2 years ago

  • Pull Request changed from https://github.com/Normation/rudder/pull/4167 to https://github.com/Normation/rudder/pull/4184
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ about 2 years ago

This bug has been fixed in Rudder 7.1.0~beta1 which was released today.

Actions
Copy link
 #8

Updated by Alexis Mousset over 1 year ago

  • Status changed from Pending release to Released
Actions
Copy link

Also available in: Atom PDF