Project

General

Profile

Bug #11285

When running "rudder agent inventory", all other reports are missing on the server

Added by Alexis MOUSSET about 1 month ago. Updated 13 days ago.

Status:
Released
Priority:
N/A
Category:
Initial promises & sys tech
Target version:
Target version (plugin):
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
50

Description

"rudder agent inventory" triggers a run containing only the inventory, but send begin/end reports, which makes the webapp consider it a full run, and compute compliance based on the received logs.

In the case, everything but the inventory is considered missing.

We should probably not send begin/end reports when not doing a full run, but this would result in losing a repaired (inventory) report on the server.


Related issues

Related to Rudder - Bug #11266: Do not send begin/end reports when running "rudder agent inventory" Rejected
Blocked by Rudder - Bug #9807: When in changes only mode, with no heartbeat, 'rudder agent run' outputs 'error: Rudder agent was interrupted during execution by a fatal error.' Released

Associated revisions

Revision a04115bb
Added by Alexis MOUSSET 28 days ago

Fixes #11285: When running \"rudder agent inventory\", all other reports are missing on the server

History

#1 Updated by Alexis MOUSSET about 1 month ago

  • Subject changed from When running "rudder agent inventory", all other reports are missing on, the server to When running "rudder agent inventory", all other reports are missing on the server

#2 Updated by Nicolas CHARLES about 1 month ago

  • Related to Bug #11266: Do not send begin/end reports when running "rudder agent inventory" added

#3 Updated by Alexis MOUSSET about 1 month ago

  • Blocked by Bug #9807: When in changes only mode, with no heartbeat, 'rudder agent run' outputs 'error: Rudder agent was interrupted during execution by a fatal error.' added

#4 Updated by Alexis MOUSSET about 1 month ago

#9807 has to be done before this one.

#5 Updated by François ARMAND 30 days ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Getting started - demo | first install | level 1 Techniques
  • Priority changed from 0 to 50

I'm categorising it as "misleading", because you are in an interactive session (so you can infer easely that that problem with reporting is what you did a moment before) and just running "rudder agent run" solve the problem.
It's typically the kind of things you are doing in a first install.

#6 Updated by Alexis MOUSSET 28 days ago

  • Status changed from New to In progress
  • Assignee set to Alexis MOUSSET

#7 Updated by Alexis MOUSSET 28 days 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-agent/pull/130

#8 Updated by Alexis MOUSSET 26 days ago

  • Status changed from Pending technical review to Pending release

#9 Updated by Vincent MEMBRÉ 13 days ago

This bug has been fixed in Rudder 4.1.7 and 4.2.0~rc1 which were released today.

#10 Updated by Vincent MEMBRÉ 13 days ago

  • Status changed from Pending release to Released

Also available in: Atom PDF