Project

General

Profile

Actions

Architecture #23084

closed

Remove constraint on component name pattern for matching reports

Added by François ARMAND over 1 year ago. Updated about 1 year ago.

Status:
Released
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Effort required:
Name check:
To do
Fix check:
To do
Regression:
No

Description

We use to match compoenent name and value pattern for matching between expected reports and actual reports.

Then, in 7.X, we added reportid which allows to better match reports and give more flexibility.
In 8.0, we want to only have match on reportid for the reports having it, and keep the old matching scheme only for report withtout reportid (== 0).
This means that component name in expected report and actual report can be totally different.

See linked issues for history / context.


Related issues 2 (0 open2 closed)

Related to Rudder - Bug #22388: Bad report maching when reportid are presentReleasedVincent MEMBRÉActions
Related to Rudder - Bug #20071: Compliance incorrectly computed when two components have the same name and cfe vars are involvedResolvedVincent MEMBRÉActions
Actions #1

Updated by François ARMAND over 1 year ago

  • Related to Bug #22388: Bad report maching when reportid are present added
Actions #2

Updated by François ARMAND over 1 year ago

  • Related to Bug #20071: Compliance incorrectly computed when two components have the same name and cfe vars are involved added
Actions #3

Updated by François ARMAND over 1 year ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #4

Updated by François ARMAND over 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/4901
Actions #5

Updated by Anonymous over 1 year ago

  • Status changed from Pending technical review to Pending release
Actions #6

Updated by Vincent MEMBRÉ about 1 year ago

  • Status changed from Pending release to Released

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

Actions

Also available in: Atom PDF