Architecture #11027
closed
We are identifying agent runs based on hasPolicyServer-*, which is inefficient, and invalid
Added by Nicolas CHARLES almost 7 years ago.
Updated over 6 years ago.
Category:
Web - Compliance & node report
Description
Only nodes with rule hasPolicyServer-* can have their reports processed by the webapp
However dsc nodes don't have this rule, so they rely on a hack to work
We ought to change the getRunsQuery in ReportsJdbcRepository to:
- remove the hasPolicyServer%
- filter on control report type
so that it would work everywhere
we ùay need to add an index on eventtype (but that's not even sure) or eventtype = 'log_info'
- Tracker changed from Bug to Architecture
- Subject changed from We are identifying agent runs based on hasPolicyServer-*, which is unefficient, and invalid to We are identifying agent runs based on hasPolicyServer-*, which is inefficient, and invalid
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
- Description updated (diff)
We decided to change the format of reports to
severity: control
technique : rudder
directive: run
serial: 0
rule: rudder
component: end/start
value : $configid
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/1688
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.2.0~beta2 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by