Project

General

Profile

Bug #15313

Policy generation error is not clear in log anymore

Added by François ARMAND 4 months ago. Updated 12 days ago.

Status:
Released
Priority:
N/A
Category:
System integration
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

Description

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.

Associated revisions

Revision 47c36778 (diff)
Added by François ARMAND 4 months ago

Fixes #15313: Policy generation error is not clear in log anymore

History

#1

Updated by François ARMAND 4 months ago

  • Status changed from New to In progress
#2

Updated by François ARMAND 4 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/2344
#3

Updated by François ARMAND 4 months ago

  • Status changed from Pending technical review to Pending release
#4

Updated by Vincent MEMBRÉ 12 days ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.0.0~beta1 which was released today.

Also available in: Atom PDF