Bug 1110365

Summary: Reports with errors on the puppet master side are not shown as failed
Product: Red Hat Satellite Reporter: Bryan Kearney <bkearney>
Component: InstallerAssignee: Dominic Cleal <dcleal>
Status: CLOSED CURRENTRELEASE QA Contact: Tazim Kolhar <tkolhar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.3CC: bbuckingham, cwelton, jmontleo, tkolhar
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/3851
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-11 12:27:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
broken module (runtime) none

Description Bryan Kearney 2014-06-17 13:49:19 UTC
If a puppet agent gets an error like "Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to parse template" or a syntax error on the puppet master, this is correctly shown as
Level "err"
Resource "Puppet"
Message "Could not retrieve catalog..."
when I click in such a report. However, when I browse reports, such reports are marked with 0 "Failed" events. I then have to search for e.g. "log ~ err" to see if such reports exist.

These Reports should be marked as failed.

Comment 1 Bryan Kearney 2014-06-17 13:49:21 UTC
Created from redmine issue http://projects.theforeman.org/issues/3851

Comment 2 Bryan Kearney 2014-06-17 13:49:31 UTC
Upstream bug assigned to dcleal

Comment 4 Bryan Kearney 2014-06-17 14:05:38 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/3851 has been closed

Comment 6 Dominic Cleal 2014-08-12 12:23:11 UTC
Created attachment 926062 [details]
broken module (runtime)

Verification steps:

1. import the attached broken module into a content view + publish
2. add the brokenmodule Puppet class to a host
3. run "service puppet restart" or "puppet agent -t" on the host
4. check for a new report with at least one failure
5. check the host is shown in error (red E) state

Comment 7 Tazim Kolhar 2014-08-13 07:00:56 UTC

the host is shown in error (red E)

Comment 8 Bryan Kearney 2014-09-11 12:27:01 UTC
This was delivered with Satellite 6.0 which was released on 10 September 2014.