Bug #26458: Errors in callback 'trigger-score-update' in the logs when a node is deleted - Rudder - Issue Tracker

Actions

Copy link

Bug #26458

open

Errors in callback 'trigger-score-update' in the logs when a node is deleted

Added by Nicolas CHARLES 6 days ago. Updated 2 days ago.

Status:

Pending release

Priority:

1 (highest)

Assignee:

François ARMAND

Category:

Web - Nodes & inventories

Target version:

8.2.6

Pull Request:

https://github.com/Normation/rudder/p...

Severity:

Minor - inconvenience | misleading | easy workaround

UX impact:

It bothers me each time

User visibility:

Effort required:

Priority:

Name check:

To do

Fix check:

To do

Regression:

Description

In Rudder 8.2, when a node a deleted, there are errors in the logs

2025-03-03 09:50:38+0000 INFO  application.authentication - Rudder authentication attempt for principal 'admin' with backend 'file': success
2025-03-03 09:50:38+0000 INFO  compliance - [metrics] global compliance (number of components): 812 [p:0 s:160 r:0 e:1 u:0 m:0 nr:41 na:234 rd:0 c:93 ana:234 nc:49 ae:0 bpm:0]
2025-03-03 09:50:46+0000 INFO  policy.generation - Node 'windows-2019.priv.normation.com' (030cff71-1c1e-4aea-beaf-e14f209396aa) is a Windows node and a we do not know how to generate a hash yet
2025-03-03 09:50:50+0000 INFO  nodes - Node 'windows-2019.priv.normation.com' [030cff71-1c1e-4aea-beaf-e14f209396aa]' was deleted
2025-03-03 09:50:51+0000 INFO  nodes - Update in node '030cff71-1c1e-4aea-beaf-e14f209396aa' inventories main information detected: triggering dynamic group update and a policy generation
2025-03-03 09:50:51+0000 DEBUG dynamic-group.timing - Check if dynamic groups may need update (false): 2ms
2025-03-03 09:50:51+0000 ERROR nodes - Error when executing callback 'trigger-score-update' on node change event [deleted] node 'windows-2019.priv.normation.com' (030cff71-1c1e-4aea-beaf-e14f209396aa
)': Inconsistency: Cannot update node '030cff71-1c1e-4aea-beaf-e14f209396aa' score
2025-03-03 09:50:51+0000 INFO  policy.generation - Start policy generation, checking updated rules

Plus, it seems the policy generation is triggered before the node is deleted, but it should be the other way around

Actions

Copy link

Updated by Nicolas CHARLES 6 days ago

Priority changed from N/A to To review

Actions

Copy link

Updated by François ARMAND 3 days ago

Subject changed from Errors in the logs when a node is deleted to Errors in callback 'trigger-score-update' in the logs when a node is deleted
Assignee set to Vincent MEMBRÉ
Priority changed from To review to 1 (highest)

Putting it to P1 because it looks like it could be a quickwin, else we will need a better qualification.

Actions

Copy link