The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #4628

Puppet does not include errors in reports

Added by Kenneth Holter almost 4 years ago. Updated over 3 years ago.

Status:AcceptedStart date:08/26/2010
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Affected Puppet version:0.25.4 Branch:
Keywords:puppet reports

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket may be automatically exported to the PUP project on JIRA using the button below:


Description

I’ve set up puppetmaster and a puppet client, both version 0.25.4. The client is set up to report back to the master (i.e. “report = true” in puppet.conf on the client). The master directs report to both “puppet_dashboard” and “store”.

The issue seems to be that when I trigger an error on the client, this error is not included in the report. I’ve attached two files to illustrate the problem: The file “output-from-client.txt” shows the client side error message, while the file “local-report.txt” shows the corresponding report. As one can see, there is no error mentioned in the report. To me this seems like a bug. Can this be confirmed?

I have not yet tested wether other error are reported back to the server.

Regards, Kenneth

Output-from-client (926 Bytes) Kenneth Holter, 08/26/2010 09:15 am

Local-report (2.43 KB) Kenneth Holter, 08/26/2010 09:15 am

History

#1 Updated by Rob McBroom almost 4 years ago

I encountered this myself a couple of weeks ago (with 0.25.5). Here’s what I think is going on. (Hopefully it will allow the devs to track it down faster.)

If Puppet encounters an error while trying to do something (add a package, file, etc.), it will report the error.

If Puppet encounters an error while getting ready to run (parsing templates, etc.), it never tries to do anything, and therefore decides there’s nothing to report.

Obviously, it would be nice to have “failed to run at all” type errors in the report as well as the “failed while running” type.

#2 Updated by Markus Roberts almost 4 years ago

  • Status changed from Unreviewed to Needs Decision

#3 Updated by Kenneth Holter almost 4 years ago

Rob McBroom wrote:

I encountered this myself a couple of weeks ago (with 0.25.5). Here’s what I think is going on. (Hopefully it will allow the devs to track it down faster.)

If Puppet encounters an error while trying to do something (add a package, file, etc.), it will report the error.

If Puppet encounters an error while getting ready to run (parsing templates, etc.), it never tries to do anything, and therefore decides there’s nothing to report.

Obviously, it would be nice to have “failed to run at all” type errors in the report as well as the “failed while running” type.

I think you’re into something here. I added this to my manifest:

package { “thisPackageDoesNotExist”: ensure => installed }

The error was included in the report. So package install fail was reported, but not manifest parsing.

#4 Updated by James Turnbull over 3 years ago

  • Assignee set to Nigel Kersten

#5 Updated by Nigel Kersten over 3 years ago

  • Status changed from Needs Decision to Accepted
  • Assignee deleted (Nigel Kersten)

We should be reporting errors that cause the entire run to fail.

Also available in: Atom PDF