Bug #8118: When a node send reports with a wrong config_id it is never marked as unresponsive - Rudder - Issue Tracker

Actions

Copy link

Bug #8118

closed

When a node send reports with a wrong config_id it is never marked as unresponsive

Bug #8118: When a node send reports with a wrong config_id it is never marked as unresponsive

Added by Alexis Mousset over 10 years ago. Updated over 10 years ago.

Status:

Released

Priority:

Assignee:

Nicolas CHARLES

Category:

Web - Compliance & node report

Target version:

3.1.11

Pull Request:

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

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

When a node sends invalid reports (for example, when the config_id is not defined and ${g.rudder_node_config_id} is sent instead), it is never considered as unresponding by the webapp, and stays in "spinning wheel" state.

The issue is not visible in the dashboard as the node is never included in compliance computation.

Related issues 1 (0 open — 1 closed)

Updated by Alexis Mousset over 10 years ago Actions
Copy link
#1

Subject changed from When a node send reports with a wrong config_id it is never to When a node send reports with a wrong config_id it is never marked as unresponsive

Updated by François ARMAND over 10 years ago Actions
Copy link
#2

Related to Bug #8051: Compliance is not correctly computed if we receive run agent right after generation added

Updated by François ARMAND over 10 years ago Actions
Copy link
#3

The code actually take care of that case, and should put the node has not responding after the grace delay (and I actually saw the state when deleting recent runs for a ndoe). So, I think the problem is a symptom of #8051, where new runs are never seen, compliance is never updated.

I propose to mark that one as a duplicate of #8051.

Updated by François ARMAND over 10 years ago Actions
Copy link
#4

In fact, the bug may be only on the list of node view, not in the backend understanding of what is the node state.

Updated by François ARMAND over 10 years ago Actions
Copy link
#5

I can't reproduce it. Alexis, do you some input about where did it happen (list of nodes ?) and if there was more set up than just having a node sending invalid id ? After a regeneration ? Etc ?