Project

General

Profile

Actions
Copy link

Bug #14474

closed

Some nodes which did not send reports for a long time appear in red instead of grey in the interface

Added by Félix DALLIDET over 5 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
5.0.15
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
55
Name check:
Fix check:
Regression:

Description

Plenty of nodes which did not sent an inventory or reports for a long period of time were listed in red in the List Nodes page instead of grey.

All the nodes concerned had the message in the 'compliance report' tab saying that they were sending reports for an old configuration (even if they had not send anything in weeks/months).
Our guess is that the red color has priority over the grey color when the last report sent was based on an outdated configuration, so the node get stuck on red forever until it respond again.

Related issues 1 (1 open — 0 closed)

Is duplicate of Rudder - Enhancement #14458: Compliance color in node list is misleading when a node hasn't answered for a long long timeNewActions
Actions
Copy link
 #1

Updated by Félix DALLIDET over 5 years ago

  • Translation missing: en.field_tag_list set to Sponsored
Actions
Copy link
 #2

Updated by Nicolas CHARLES over 5 years ago

  • Related to Enhancement #14458: Compliance color in node list is misleading when a node hasn't answered for a long long time added
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.9 to 5.0.10
Actions
Copy link
 #4

Updated by Benoît PECCATTE over 5 years ago

  • Subject changed from Some nodes which did not send reports for a long time appear in red instead of hrey in the interface to Some nodes which did not send reports for a long time appear in red instead of grey in the interface
  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 65
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.10 to 5.0.11
  • Priority changed from 65 to 64
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.11 to 5.0.12
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 5.0.12 to 5.0.13
  • Priority changed from 64 to 62
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.13 to 5.0.14
  • Priority changed from 62 to 60
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ about 5 years ago

  • Target version changed from 5.0.14 to 5.0.15
  • Priority changed from 60 to 59
Actions
Copy link
 #10

Updated by François ARMAND about 5 years ago

  • Status changed from New to Rejected
  • Priority changed from 59 to 58

This is a duplicate of #14458, I'm closing it.

Actions
Copy link
 #11

Updated by François ARMAND about 5 years ago

  • Related to deleted (Enhancement #14458: Compliance color in node list is misleading when a node hasn't answered for a long long time)
Actions
Copy link
 #12

Updated by François ARMAND about 5 years ago

  • Is duplicate of Enhancement #14458: Compliance color in node list is misleading when a node hasn't answered for a long long time added
Actions
Copy link
 #13

Updated by Alexis Mousset over 2 years ago

  • Priority changed from 58 to 55
Actions
Copy link

Also available in: Atom PDF