Rudder

Is this still broken? If so, it needs fixing ASAP!

Starting with a fresh set of data, we weren't able to reproduce it like that.

None the less, we were able to see intermitent phase were the reports were switching from a normal displaying (mostly success/no answer/errors) to a only missing/unexpected one.

The interpretation from code point of view is that at some point, we must be expecting reports for a given version of the policy configuration and got reports for an other one (so that all expected reports were missing and we get a bunch of unexpected ones). Given the transitionnal and periodic charachterisation of the state, I would guess that some computation regarding the lenght of a era where a give configuration is OK are buggy. For now, I didn't successed in crafting failing test nor reproducing the pb in a consistent manner.

One other strange behaviour with unexpected/missing reports:

A rule R1 exists, with D1 / G1.
A rule R2 is created, also with D1 / G1.
Then, R2 is correclty displayed as "applying", but R1 display "missing reports"

François ARMAND wrote:

One other strange behaviour with unexpected/missing reports:

A rule R1 exists, with D1 / G1.
A rule R2 is created, also with D1 / G1.
Then, R2 is correclty displayed as "applying", but R1 display "missing reports"

this looks a lot like http://www.rudder-project.org/redmine/issues/6020

This may be fixed by https://github.com/Normation/rudder/pull/741 , but since we couldn't reliably reproduce it, i am not sure

It seems more likely that the problem was the missing "complete == true" when looking for new run information, corrected in https://github.com/Normation/rudder/pull/743 (#6040)