Project

General

Custom queries

Profile

Actions
Copy link

Bug #24556

closed

origin of config report is N/A

Added by Anonymous over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Marek Hulán
Category:
Puppet Reports
Target version:
1.19.0
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/5941, https://github.com/theforeman/foreman/pull/5952
Fixed in Releases:
1.19.0
Found in Releases:
1.18.0, 1.18.0-RC1, 1.18.0-RC2, 1.18.0-RC3, 1.18.1, 1.18.2, 1.19.0, 1.19.0-RC1, 1.19.0-RC2
Red Hat JIRA:

Description

When a puppet report contains only two lines like the following example, the column "Origin" of the report table shows N/A, though it s a report from Puppet.

content changed '{md5}085471495a8a34d24cfda019bccbe7ad' to '{md5}fc037522c6f4a510394eaeb352067ff6'
Puppet     Applied catalog in 0.32 seconds
Actions
Copy link
 #1

Updated by Anonymous over 6 years ago

replacing .first by .last in /usr/share/foreman/app/services/report_scanner/puppet_report_scanner.rb fixed it. I m not sure if this hack is the way to handle report logs..

Actions
Copy link
 #3

Updated by Marek Hulán over 6 years ago

Thanks, I was able to reproduce. Could you please check whether the patch fixes the problem for you?

Actions
Copy link
 #6

Updated by Anonymous over 6 years ago

Yes, it fixes the problem.

Actions
Copy link
 #8

Updated by Marek Hulán over 6 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link

Also available in: Atom PDF