Bug #19615
closedCompliance problem in 7.0
Description
I applied an MOTD directive on a node, and received a run from this node.
It shows missing reports for motd
yet it is in the technical log
Files
Updated by Nicolas CHARLES about 3 years ago
- Translation missing: en.field_tag_list set to Blocks 7.0-beta
Updated by Nicolas CHARLES about 3 years ago
So, after investigation, for a given node, when there is a missing, it's because getExecutionReports doesn't return any reports.
It looks for reports AgentRunId(NodeId(a8f00955-7a4c-4e1e-8578-f4ef7909fcc0),2021-08-03T11:13:45.000+02:00)
But there is no run in ruddersysevents with an executiontimestamp of 11:13:45.000+02:00 for this node
8940 | 2021-08-03 11:13:46+02 | a8f00955-7a4c-4e1e-8578-f4ef7909fcc0 | inventory-all | inventory-all | 0 | inventory | None | 20 21-08-03 11:13:46+02 | result_success | Inventory | Next inventory scheduled between 00:00 and 06:00
even considering executiondate, it is
8928 | 2021-08-03 11:13:46+02 | a8f00955-7a4c-4e1e-8578-f4ef7909fcc0 | run | rudder | 0 | start | 20210802-174301-fafcc7a4 | 20 21-08-03 11:13:46+02 | control | Common | Start execution
Yet, in reportsexecution, there is this timestamp, which causes the error
a8f00955-7a4c-4e1e-8578-f4ef7909fcc0 | 2021-08-03 11:13:45+02 | 20210802-174301-fafcc7a4 | 8928 | 2021-08-03 09:13:48.422369 | 2021-08-03 11:13:52.208357
other node don't have this value either
Updated by Alexis Mousset about 3 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset about 3 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/3771
Updated by Alexis Mousset about 3 years ago
The inserted timestamp was the timestamp of the agent start (i.e. rudder agent run
command) and not the timestamp of the first report, which is what the webapp expects.
Updated by Alexis Mousset about 3 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|dab60c621c504dcb3c163a712fe0afe3c3f97f7b.
Updated by Vincent MEMBRÉ about 3 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.0.0~beta1 which was released today.