Actions
Bug #17349
closed
Disable sending old reports from relayd
Status:
Released
Priority:
N/A
Assignee:
Category:
System techniques
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
relayd has a feature that allows to send old report it received while it was shut down. But that feature lead to complicated problem reguarding compliance (#17180).
So until we are able to compute compliance reliably for reports in the past, historize it correctly, and know how to deal with edge cases, we relay should only send old reports in order it got them and never send a report received before an other if that other was already sent. So: when relayd restart, do whatever but in reception chronological order, and on permanent run, only send new runs.
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 Alexis Mousset over 4 years ago
- Category changed from Relay server or API to System techniques
Updated by Alexis Mousset over 4 years ago
- Status changed from New to In progress
Updated by Alexis Mousset over 4 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to François ARMAND
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1593
Updated by Alexis Mousset over 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|b951728745e3998ac8d929f28c56302f343a8989.
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.0~beta3 which was released today.
Updated by François ARMAND about 4 years ago
- Has duplicate Bug #17181: Old runlog catchup by relayd breaks compliance computation added
Actions