Project

General

Profile

Actions
Copy link

Bug #1363

closed

Report with a failed catalog compile is not a failed report (Patch provided)

Added by Raffael Schmid about 13 years ago. Updated almost 13 years ago.

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

Description

When we wanted to use the failed_report_email_notification option, we discovered that reports which come from a failed catalog run are not considered as failed.

This wrong assumption happens in ReportCommon.error? which searches only for failed action inside the report (service start failed for example).

I added a patch and sent it to the mailinglist: https://groups.google.com/group/foreman-dev/browse_thread/thread/fce80bcc18bc1226

It just adds a check for severity of the loglines inside the report.

Actions
Copy link
 #1

Updated by Raffael Schmid almost 13 years ago

please close, this was caused by the puppet client version which was smaller than 2.6.5

Actions
Copy link
 #2

Updated by Ohad Levy almost 13 years ago

  • Status changed from New to Resolved
Actions
Copy link

Also available in: Atom PDF