Policy generation error is not clear in log anymore
Now that we always show how much time a policy generation took, even in case of error, if we just glance at the log we can miss a failed generation for a successful one:
[2019-07-25 16:03:44] DEBUG policy.generation - Node's target configuration built in 1707 ms, start to update rule values. [2019-07-25 16:03:45] INFO policy.generation - Configuration of following 104 nodes were updated, their promises are going to be written: [...] [2019-07-25 16:03:45] DEBUG policy.generation - Reports updated in 91 ms [2019-07-25 16:03:45] DEBUG policy.generation - Paths computed and templates read in 412 ms [2019-07-25 16:03:46] DEBUG policy.generation - Promises prepared in 208 ms [2019-07-25 16:03:47] DEBUG policy.generation - Promises written in 1324 ms [2019-07-25 16:03:47] DEBUG policy.generation - Properties written in 25 ms [2019-07-25 16:03:47] DEBUG policy.generation - Parameters written in 22 ms [2019-07-25 16:03:48] INFO policy.generation - Policy generation completed in: 9 s [2019-07-25 16:03:48] ERROR policy.generation - Error when updating policy, reason was: Cannot write nodes configuration <- Error when executing hooks:
We need to change the
Policy generation completed in: 9 s into
Policy generation failed in: 9 s in that case.