Project

General

Profile

Actions

Bug #14380

closed

Improve message on Node compliance details when reports are outdated

Added by Nicolas CHARLES over 5 years ago. Updated over 5 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
80
Name check:
Fix check:
Regression:

Description

A node has out of date policies (4 days old) but it is reassuringly blue, and say that it is expected

This node has recently been assigned a new policy but no reports have been received for the new policy yet.

This is expected, the node is reporting on the previous configuration policy and should report on the new one at latest 2019-02-26 11:04:00. Previous known states are displayed below. The latest reports received for this node are from a run started at 2019-02-26 10:44:00 with configuration ID 20190216-063300-4d41349f.

Current configuration ID for this node is '20190222-161922-28d22b2e' (generated on 2019-02-22 16:19:22).

it should state that it is really too old

happen on Rudder 5.0, most likely in 4.3


Files

reporting.png (17.2 KB) reporting.png Nicolas CHARLES, 2019-02-26 10:48
Actions

Also available in: Atom PDF