Project

General

Profile

Actions
Copy link

Bug #17181

closed

Old runlog catchup by relayd breaks compliance computation

Added by Alexis Mousset about 4 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Web - Compliance & node report
Target version:
6.0.10
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
43
Name check:
To do
Fix check:
To do
Regression:

Description

The webapp expects reports to be inserted in the chronological order into the database, but it is not guaranted anymore with HTTP reporting, specially with the catchup feature that processes new runlogs in priority and then backfills old ones.

Related issues 2 (1 open — 1 closed)

Related to Rudder - Architecture #17180: Compliance incorrectly computed with old reports or runs not sent in node chronological orderNewFrançois ARMANDActions
Is duplicate of Rudder - Bug #17349: Disable sending old reports from relaydReleasedFrançois ARMANDActions
Actions
Copy link

Also available in: Atom PDF