Bug #14995
Updated by Nicolas CHARLES almost 5 years ago
One node sends reports from a configuration dating 15:22 Several policy generation happened in a row since, and i get following status <pre> This node has recently been assigned a new policy but no reports have been received for the new policy yet. This is expected, the node is reporting on the previous configuration policy and should report on the new one at latest 2019-05-30 19:34:06. Previous known states are displayed below. The latest reports received for this node are from a run started at 2019-05-30 19:24:06 with configuration ID 20190529-155230-4fa56379. Current configuration ID for this node is '20190530-191237-a0dac60d' (generated on 2019-05-30 19:12:37). </pre> Every time, so, regenerating once causes the "should report on the latest one" is in 10 minutes webapp to ignore invalid compliance