Project

General

Profile

Actions
Copy link

Enhancement #14458

open

Compliance color in node list is misleading when a node hasn't answered for a long long time

Added by Nicolas CHARLES over 5 years ago. Updated about 1 year ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
Ideas (not version specific)
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Name check:
Fix check:
Regression:

Description

I have 2 nodes which haven't answered in a long time
debian-5-64 hasn't answered since 7/3/2019, ubuntu since 12/03/2019

both should be in gray, but first one is red

explanation for debian explains it all: we don't know anymore the configuration ID - so we claim we don't know it

for ubuntu, we know the config id, so it's gray

Gray (no answer) should have precedence over unknown (red)

Files

Download all files
list.png (16.3 KB) list.png Nicolas CHARLES, 2019-03-13 11:16
debian.png (34.8 KB) debian.png Nicolas CHARLES, 2019-03-13 11:16
ubuntu.png (30.1 KB) ubuntu.png Nicolas CHARLES, 2019-03-13 11:18

Related issues 2 (1 open — 1 closed)

Related to Rudder - Bug #14995: When node configuration is updated, status becomes pending even if the node is sending very old reportsNewActions
Has duplicate Rudder - Bug #14474: Some nodes which did not send reports for a long time appear in red instead of grey in the interfaceRejectedActions
Actions
Copy link

Also available in: Atom PDF