Project

General

Profile

Actions

Bug #21007

closed

Techniques with no component define have no reporting

Added by Vincent MEMBRÉ 7 months ago. Updated 6 months ago.

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

Description

Prior 7.0, we had a system that automatically defined expected reports when a technique was not defining explicit reports (like aptPackageManagerSettings )

The fallback was to generate a component with value (technique name, ie aptPackageManagerSettings) and value None.

We changed in 7.0, how this case was treated, and we know don't expect any value. we should adapt the algorithm to treat this case

Actions #1

Updated by Vincent MEMBRÉ 7 months ago

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

Updated by Vincent MEMBRÉ 7 months ago

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

Updated by Vincent MEMBRÉ 7 months ago

  • Status changed from In progress to Pending release
Actions #6

Updated by Vincent MEMBRÉ 6 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 7.0.3 which was released today.

Actions

Also available in: Atom PDF