Rudder

A generic methods called twice with the same parameters will produce a single report whereas Rudder expect 2 reports.

Since this is an expected behaviour of cfengine we should have a process that works with it.

First, the rudder logger in ncf is controlled by Rudder. Second, it has everything needed to do proper reporting.
So we can guess missing reports from existing reports.

Here is the proposed solution :
- change ncf rudder_logger to log to a temporary file in addition to syslog
- have a new bundle in rudder generated bundlesquence named complete_reports and called at the end en the sequence
- this bundle would read the temporary file and read the expected report.csv
- on each missing report, if a report already exists for the same parameters, it means that the outcome is exactly the same
- append to syslog a copy of this report to make Rudder happy
- remove the temporary file