Project

General

Profile

Actions
Copy link

Bug #12700

closed

Failing puppet runs report as ok.

Added by Martin Hovmöller about 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

We have a number of hosts that are failing their puppet runs with errors like this:
Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node <host>: Failed to find <host> via exec: Execution of '/etc/puppet/node.rb <host>' returned :

Even though the puppet run clearly fails foreman reports some of these nodes as ok with a "no changes" status.

Actions
Copy link
 #1

Updated by Dominic Cleal about 9 years ago

  • Status changed from New to Need more information

Perhaps pastebin your report processor? There was a fix a very long ago to the processor in #3851 to count these types of failures as a resource error, in lieu of Puppet itself reporting this.

Actions
Copy link
 #2

Updated by Martin Hovmöller about 9 years ago

  • Status changed from Need more information to Closed
  • % Done changed from 0 to 100

I didn't realize node.rb wasn't updated with new releases. Our node.rb was apparenly from April 2014.
I can't really say if updating node.rb fixed this specific problem, because the puppet runs actually complete now. :)

So this was probably just a case of bad usage, although maybe this should be noted in the Upgrade-part of the manual?
Anyway, I'll close the issue, thanks for the help.

Actions
Copy link

Also available in: Atom PDF