Project

General

Profile

Actions
Copy link

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.

Status:
Released
Priority:
4
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)

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

Updated by Alexis Mousset over 8 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
Copy link
 #2

Updated by François ARMAND over 8 years ago

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

Updated by François ARMAND over 8 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
Copy link
 #4

Updated by François ARMAND over 8 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
Copy link
 #5

Updated by François ARMAND over 8 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
Copy link
 #6

Updated by Alexis Mousset over 8 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
Copy link
 #7

Updated by François ARMAND over 8 years ago

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

Updated by François ARMAND over 8 years ago

  • Status changed from New to In progress
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.11 to 3.1.12
Actions
Copy link
 #10

Updated by François ARMAND over 8 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
Copy link
 #11

Updated by François ARMAND over 8 years ago

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

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.12 to 3.1.11
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ over 8 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
Copy link

Also available in: Atom PDF