Actions
Bug #5797
closedForeman does not flag catalog retieve failures as a puppet failure if the cached catalog runs without issues
Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Reporting
Target version:
-
Description
Foreman does not log any failures when a puppet can not retrieve a catalog from the remote server if puppet fails back to a cached catalog and the run finishes without errors.
logs: - !ruby/object:Puppet::Util::Log message: "Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid relationship: File[/etc/mcollective/ssl/public.pem] { require => File[/etc/mcollective/ssl] }, because File[/etc/mcollective/ssl] doesn't seem to be in the catalog" level: !ruby/sym err tags: - err time: 2014-05-19 17:11:01.294604 +00:00 source: Puppet - !ruby/object:Puppet::Util::Log message: "Using cached catalog" level: !ruby/sym notice tags: - notice time: 2014-05-19 17:11:03.743133 +00:00 source: Puppet - !ruby/object:Puppet::Util::Log message: "Finished catalog run in 37.88 seconds" level: !ruby/sym notice tags: - notice time: 2014-05-19 17:11:44.763923 +00:00 source: Puppet
Updated by Dominic Cleal over 10 years ago
- Is duplicate of Bug #3851: Reports with errors on the puppet master side are not shown as failed added
Updated by Dominic Cleal over 10 years ago
- Status changed from New to Feedback
This should be fixed with the change in #3851, would you mind testing this updated report processor? https://raw.githubusercontent.com/theforeman/puppet-foreman/master/templates/foreman-report_v2.rb.erb
Updated by Dominic Cleal over 10 years ago
- Status changed from Feedback to Duplicate
Great, thanks for testing.
Actions