Project

General

Profile

Actions

Bug #8118

closed

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

Added by Alexis MOUSSET about 5 years ago. Updated almost 5 years ago.

Status:
Released
Priority:
4
Category:
Web - Compliance & node report
Target version:
Severity:
User visibility:
Effort required:
Priority:

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

Related to Rudder - Bug #8051: Compliance is not correctly computed if we receive run agent right after generationReleasedNicolas CHARLES2016-05-19Actions
Actions #1

Updated by Alexis MOUSSET about 5 years ago

  • 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
Actions #2

Updated by François ARMAND almost 5 years ago

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

Updated by François ARMAND almost 5 years ago

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.

Actions #4

Updated by François ARMAND almost 5 years ago

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

Actions #5

Updated by François ARMAND almost 5 years ago

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 ?

Actions #6

Updated by Alexis MOUSSET almost 5 years ago

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.

Actions #7

Updated by François ARMAND almost 5 years ago

  • Priority changed from N/A to 4
  • Target version set to 3.1.11
Actions #8

Updated by François ARMAND almost 5 years ago

  • Status changed from New to In progress
Actions #9

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.1.11 to 3.1.12
Actions #10

Updated by François ARMAND almost 5 years ago

  • 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
Actions #11

Updated by François ARMAND almost 5 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #12

Updated by Vincent MEMBRÉ almost 5 years ago

  • Target version changed from 3.1.12 to 3.1.11
Actions #13

Updated by Vincent MEMBRÉ almost 5 years ago

  • 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.

Actions

Also available in: Atom PDF