Bug #2163

puppetrun does not know when client runs fail

Added by Pete Emerson over 1 year ago. Updated about 1 year ago.

Status:Accepted Start:04/15/2009
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:executables
Target version:unplanned
Affected version:0.24.7 Branch:
Keywords:
Votes: 0

Description

I intentionally broke my puppet_node_classifier to see exit codes.

See also: http://projects.reductivelabs.com/issues/2162

puppetd prints out that there is a problem:

/usr/sbin/puppetd —server=01.demo.test —test

err: Could not retrieve catalog: Could not find node ‘01.demo.test’; cannot compile warning: Not using cache on failed catalog

puppetrun, however, merrily thinks that everything is okay:

puppetrun —host=01.demo.test —foreground

Failed to load ruby LDAP library. LDAP functionality will not be available Triggering 01.demo.test 01.demo.test finished with exit code 0 Finished

The exit code I’ve submitted in the previous bug, but I think puppetrun should give me an indication of whether there were any problems with the run.

Context, in case it’s helpful:

I’m controlling puppet via a web interface, and want to take an action across a cluster of machines, like “upgrade these servers to a new version of an application”. puppet_node_classifier pulls from a database, and then the nodes update themselves according to the rules laid out. I want to be able to indicate in the web interface whether the upgrade was successful or not. Currently, it looks to me that puppetrun is only reporting whether or not the trigger of a manual run was successful, and not whether the manual run itself was successful.

Pete

History

Updated by Pete Emerson over 1 year ago

Note that I see Luke’s comment on ticket 2161, please review, this might just be a duplicate of that ticket.

Pete

Updated by James Turnbull over 1 year ago

  • Category set to executables
  • Status changed from Unreviewed to Needs more information
  • Assignee set to Luke Kanies
  • Target version set to unplanned

Updated by Luke Kanies over 1 year ago

  • Subject changed from Puppetrun and puppetd disagree to puppetrun does not know when client runs fail
  • Status changed from Needs more information to Accepted
  • Assignee changed from Luke Kanies to Puppet Community

That’s probably right. ‘puppetrun’ doesn’t have good means of getting data back from the client.

Of course, give that, puppetrun is correct – the run was triggered, it just doesn’t know what happened next.

Updated by James Turnbull about 1 year ago

  • Assignee deleted (Puppet Community)

Also available in: Atom PDF