Project

General

Profile

Bug #15085

Bug #14465: Generation fails with "Task FutureTask rejected from ThreadPoolExecutor" due to timeout in JS computation

When a policy generation is triggered but nothing needs to be updated a log erroneously states that all nodes failed

Added by Nicolas CHARLES about 1 year ago. Updated about 1 year ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Severity:
User visibility:
Effort required:
Priority:
0

Description

When receiving an inventory, a policy generation was triggered, and no node were to be updated

however logs says:

[2019-06-14 04:03:50] INFO  com.normation.rudder.services.policies.BuildNodeConfiguration - There are 2743 nodes in success at the enf of NodeConfiguration
[2019-06-14 04:03:50] DEBUG policy.generation - Node's target configuration built in 143074 ms, start to update rule values.
[2019-06-14 04:03:53] WARN  report - Not updating changes by rule - disabled by settings 'rudder_compute_changes'
[2019-06-14 04:03:54] DEBUG policy.generation - Not updating non-modified node configuration: [99a996b5-2e23-426f-b7b4-e0b6e1d5cbe0,
...
[2019-06-14 04:04:19] INFO  policy.generation - Number of nodes updated       :          0   
[2019-06-14 04:04:19] WARN  policy.generation - Nodes in errors (2743): 

the detection of node in error is incorrect

#1

Updated by Vincent MEMBRÉ about 1 year ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ
#2

Updated by Vincent MEMBRÉ about 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/2267
#3

Updated by Vincent MEMBRÉ about 1 year ago

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

Updated by Alexis MOUSSET about 1 year ago

  • Subject changed from At the end of policy generation, there is a message about all the nodes that didn't need to be updated that is an error message to When a policy generation is triggered but nothing needs to be updated a log erroneously states that all nodes failed
#9

Updated by Vincent MEMBRÉ about 1 year ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.12 which was released today.

Also available in: Atom PDF