Actions
Bug #17181
closed
Old runlog catchup by relayd breaks compliance computation
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.
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.0.6 to 6.0.7
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.0.7 to 6.0.8
Updated by François ARMAND over 4 years ago
- Related to Architecture #17180: Compliance incorrectly computed with old reports or runs not sent in node chronological order added
Updated by François ARMAND over 4 years ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 50
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.0.8 to 6.0.9
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.0.9 to 6.0.10
- Priority changed from 50 to 49
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.0.10 to 798
- Priority changed from 49 to 48
Updated by François ARMAND about 4 years ago
- Status changed from New to Resolved
- Priority changed from 48 to 47
Duplicate of #17349
Updated by François ARMAND about 4 years ago
- Is duplicate of Bug #17349: Disable sending old reports from relayd added
Updated by Benoît PECCATTE over 3 years ago
- Target version changed from 798 to 6.0.10
- Priority changed from 47 to 43
Actions