Bug #8118
closed
When a node send reports with a wrong config_id it is never marked as unresponsive
Added by Alexis Mousset over 8 years ago.
Updated over 8 years ago.
Category:
Web - Compliance & node report
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.
- 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
- Related to Bug #8051: Compliance is not correctly computed if we receive run agent right after generation added
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.
In fact, the bug may be only on the list of node view, not in the backend understanding of what is the node state.
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 ?
Reproduced on 3.1.9.
3.1.10 fixes the Reports tab, with a helping message, but the node is still spinning in the node list.
- Priority changed from N/A to 4
- Target version set to 3.1.11
- Status changed from New to In progress
- Target version changed from 3.1.11 to 3.1.12
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/1113
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Target version changed from 3.1.12 to 3.1.11
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.11 and 3.2.4 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by