Project

General

Profile

Actions
Copy link

Bug #15085

closed

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 over 5 years ago. Updated over 5 years ago.

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
Web - Config management
Target version:
5.0.12
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:

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

Actions
Copy link

Also available in: Atom PDF