Actions
Bug #24556
closed
origin of config report is N/A
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:
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
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..
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Assignee set to Marek Hulán
- Pull request https://github.com/theforeman/foreman/pull/5941 added
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?
Updated by Tomer Brisker over 6 years ago
- Target version set to 1.19.0
- Fixed in Releases deleted (
1.19.0)
Updated by Tomer Brisker over 6 years ago
- Fixed in Releases 1.19.0, 1.20.0 added
- 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-RC2 added
Updated by Marek Hulán over 6 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset 3af8b327bb67ebbfd21d6f3bfbacea2e8f85001f.
Updated by The Foreman Bot over 6 years ago
- Pull request https://github.com/theforeman/foreman/pull/5952 added
Actions