Project

General

Profile

Actions
Copy link

Bug #22375

closed

Nodes not answering are seen in "missing" rather than in "no reports"

Added by Nicolas CHARLES almost 2 years ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - Compliance & node report
Target version:
7.2.5
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I hate Rudder for that
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Small
Priority:
171
Name check:
To do
Fix check:
Checked
Regression:
Yes

Description

Nodes with litterally no reports are seen in missing in the compliance rather than no reports because their configId is not known

I have already seen this issue (but I can't find the ticket) and to reproduce it, it may a node offline AND policy generation that changes the node config id for its policy (it may or may not be important to have outdated nodeconfigid as well)
The system is in change only reporting, it may or may not be relevant

Step to reproduce:
  • have a node offline
  • that as a last run non empty (doing insert into reportsexecution values ( '13d97019-f5ab-4f1f-8846-fdf36c0a7d45', '2023-01-10 00:00:00+01', '20230111-112830-e13bcefb', 314643008, '2023-01-14 23:00:47.293154', '2023-02-11 23:10:47.293154' ); is enough to create a last run date
  • restart rudder-jetty
  • see that the node is in "missing" (red) rather than "no reports" (grey)

Subtasks 1 (0 open — 1 closed)

Bug #22381: Add unit test for the missing/unexpected parent issue on old runsReleasedFrançois ARMANDActions

Related issues 2 (0 open — 2 closed)

Has duplicate Rudder - Bug #19942: reporting states that node sends out of date reports rather than the node sent reports too long agoRejectedActions
Has duplicate Rudder - Bug #15907: Changes-only does not behave as expected and lead to missing reportsRejectedActions
Actions
Copy link

Also available in: Atom PDF