Rudder

I forgot to put the question ... so the question is : is it normal ?

This is a really interesting bug. I'm currently evaluating the impact.

Simply to change the way the reports are count is going to be a big task, and it will probably cause some compatibility issues with the techniques, as it might put in light some unfound bugs....

I see two quick fixes to do here:

1) Fix the reporting "counting" (second part of Nicolas' comment #4) so that we check that we have exactly the right number of reports for each component/key in a given PI. This should have been the case already, and was spotted thanks to this bug. This part will be handled in this ticket, and we should have a fix ready and tested by Thursday morning.

As a side effect, this will cause the case 1) reported by François (2 "postfix install" sections in the same PI) to produce 0% compliance, in the same way that the case 2) does. This is because all configuration for these two packages is identical ("postfix" and "install only"), so CFEngine detects this and only send one report, where we are expecting two.

2) To avoid this, I think that adding a mecanism to avoid duplicated identical sections would make sense. Two approaches are detailed in #2424 :
2.1) Silently drop any duplicated sections. This could be confusing for the user, but will avoid breaking reporting, and is in effect not deleting any data since we delete only an exact copy of existing data. This is a "quick win"...
2.2) Warn the user he's input a duplicate section and ask him what to do. This takes a bit longer, which is why we're considering 2.1 first.

Applied in changeset 678f614c3d11cc06cf7d8d64bb42b998940ed806.

The proposal looks ok, thank you Francois !