Actions
Bug #22655
closedAlways send start/end reports even in changes-only mode
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
Currently it is skipped unless we have a repaired/error report, but this leads to invalid runlogs being sent to the server.
As in HTTP reporting mode a report is sent for every agent run, let's make it valid.
More precisely:
- When we have old techniques making hard-coded reports, we have runlogs containing valid reports without a start/end (as the detection mechanism is in the new reporting methods), and relayd logs a
Missing start/end control reports in runlog, no config id available
. - When we have no report at all, we still have all CFEngine logs and relayd cannot affect them to a report, which leads to
Invalid report
logs.
This might have a very slight performance impact on the server as more reports will be inserted in the database.
Updated by Alexis Mousset over 1 year ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset over 1 year ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Félix DALLIDET
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1813
Updated by Alexis Mousset over 1 year ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|dddd5bf33de5acf0891a255e5840d633e890d8be.
Updated by Alexis Mousset over 1 year ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ over 1 year ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.2.6 and 7.3.1 which were released today.
Actions