Project

General

Profile

Actions
Copy link

Bug #21007

closed

Techniques with no component define have no reporting

Added by Vincent MEMBRÉ about 2 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - Compliance & node report
Target version:
7.0.3
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
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
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/4242
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ about 2 years ago

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

Updated by Elaad FURREEDAN about 2 years ago

  • Fix check changed from To do to Checked
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ almost 2 years ago

  • Status changed from Pending release to Released

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

Actions
Copy link

Also available in: Atom PDF