Project

General

Profile

Actions

Bug #10751

closed

Add a warn message when agent run is incomplete

Added by Florian Heigl over 7 years ago. Updated almost 6 years ago.

Status:
Released
Priority:
N/A
Category:
Agent
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Small
Priority:
31
Name check:
Fix check:
Regression:

Description

Hi,

I'm not sure if this is the same error as anywhere else, but just to be safe:

If I get a specific bundle, I get most confusing output.

root@rudder:/var/rudder/configuration-repository/techniques/system# rudder agent run -b sendInventoryToCmdb
Rudder agent 4.1.1-jessie0 (CFEngine Core 3.10.0)
Node uuid: root
Start execution with config [20170517-121308-dc93beed]

M| State         Technique                 Component                 Key                Message
E| compliant     DistributePolicy          Send inventories to CMDB                     Incoming inventories were successfully added to Rudder
error    Rudder agent was interrupted during execution by a fatal error
         Run with -i to see log messages.

## Summary #####################################################################
1 components verified in 2 directives
   => 1 components in Enforce mode
      -> 1 compliant
execution time: 4.35s
################################################################################@

as far as I can tell:
- summary is correct
- message: starts with "E" - which is likely wrong
- if it were an "E" it should not be green, right?
- Message text says everything is fine
- And then there's a generic error that calls for doing -i

So, it's 4-way contradictive, and I suspect it's also unique 4 errors behind this.

It's misleading and there is no workaround, expect not trusting rudder's output.


Subtasks 1 (0 open1 closed)

Bug #13821: Document that "rudder agent run -b" should not be used except if support asksReleasedBenoît PECCATTEActions

Related issues 2 (0 open2 closed)

Related to 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.'ReleasedNicolas CHARLESActions
Related to Rudder - Bug #13882: rudder agent inventory wrongly states that we are not in full compliance modeReleasedAlexis MoussetActions
Actions #1

Updated by François ARMAND over 7 years ago

  • User visibility changed from First impressions of Rudder to Infrequent - complex configurations | third party integrations
  • Effort required set to Small
  • Priority changed from 0 to 14
Actions #2

Updated by François ARMAND over 7 years ago

  • Related to 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
Actions #3

Updated by Jonathan CLARKE over 7 years ago

Florian Heigl wrote:

M| State Technique Component Key Message
E| compliant DistributePolicy Send inventories to CMDB Incoming inventories were successfully added to Rudder

- message: starts with "E" - which is likely wrong
- if it were an "E" it should not be green, right?

Just on this one point: the letter "E" in the "M" column here reprensents the directives's "mode" - Enforce (E) or Audit (A). It's not an error - Enforce is green, and Audit is blue.

Actions #4

Updated by Benoît PECCATTE over 7 years ago

  • Priority changed from 14 to 25
Actions #5

Updated by Benoît PECCATTE almost 7 years ago

  • Priority changed from 25 to 35
Actions #6

Updated by Benoît PECCATTE over 6 years ago

  • Priority changed from 35 to 33

'E' means enforce.
The agent has been interrupted by a fatal error not show here (fatal error rarely have time to produce an error).
Running again with -i would probably give more information about what happened before the error.
There is an error message in red saying that there was a fatal error.
An now there's even a proper return code.

So i don't see what we could change here.

Actions #7

Updated by Florian Heigl over 6 years ago

Hi,

start with making the "Summary" report that the agent run FAILED

Actions #8

Updated by Alexis Mousset almost 6 years ago

  • Description updated (diff)
  • Priority changed from 33 to 31
Actions #9

Updated by Alexis Mousset almost 6 years ago

  • Subject changed from incorrect reporting with partial runs to Incorrect reporting with partial runs
Actions #10

Updated by Alexis Mousset almost 6 years ago

  • Assignee set to Alexis Mousset
  • Target version set to 4.3.7
Actions #11

Updated by Alexis Mousset almost 6 years ago

  • Status changed from New to In progress
Actions #12

Updated by Alexis Mousset almost 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Alexis Mousset to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-agent/pull/195
Actions #13

Updated by Alexis Mousset almost 6 years ago

  • Status changed from Pending technical review to Pending release
Actions #14

Updated by Nicolas CHARLES almost 6 years ago

  • Subject changed from Incorrect reporting with partial runs to Add a warn message when agent run is incomplete
Actions #15

Updated by Vincent MEMBRÉ almost 6 years ago

This bug has been fixed in Rudder 4.3.7 and 5.0.3 which were released today.
Changelog
Changelog
Actions #16

Updated by Vincent MEMBRÉ almost 6 years ago

This bug has been fixed in Rudder 4.3.7 and 5.0.3 which were released today.
Changelog
Changelog
Actions #17

Updated by Vincent MEMBRÉ almost 6 years ago

  • Related to Bug #13882: rudder agent inventory wrongly states that we are not in full compliance mode added
Actions #18

Updated by Vincent MEMBRÉ almost 6 years ago

  • Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.7 and 5.0.3 which were released today.
Changelog
Changelog
Actions

Also available in: Atom PDF