Project

General

Profile

Actions
Copy link

Bug #35833

open

Puppet configuration reports without entries do not get an origin

Added by Ewoud Kohl van Wijngaarden almost 2 years ago. Updated over 1 year ago.

Status:
Ready For Testing
Priority:
Normal
Assignee:
Ewoud Kohl van Wijngaarden
Category:
Puppet Reports
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
2192939
Pull request:
https://github.com/theforeman/foreman/pull/9536, https://github.com/theforeman/puppet-puppetserver_foreman/pull/29
Fixed in Releases:
Found in Releases:
3.4.0, 3.5.0
Red Hat JIRA:

Description

Since #35684 Puppet reports without messages can come in. The current Puppet report scanner looks at the last log message to determine the source, but if there is no message there is no way to identify it.

It would probably be best to add an explicit field for the origin, but the current API does not expose this.

https://community.theforeman.org/t/identify-config-report-origin/31465 has a more detailed analysis.

Related issues 1 (0 open — 1 closed)

Related to Installer - Bug #35684: Filter "Applied catalog in x.y seconds" messages out of Puppet reportClosedEwoud Kohl van WijngaardenActions
Actions
Copy link

Also available in: Atom PDF