Project

General

Profile

Bug #35833

Puppet configuration reports without entries do not get an origin

Added by Ewoud Kohl van Wijngaarden about 2 months ago. Updated about 1 month ago.

Status:
Ready For Testing
Priority:
Normal
Assignee:
Ewoud Kohl van Wijngaarden
Category:
Puppet Reports
Target version:
3.5.2
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/9536
Fixed in Releases:
Found in Releases:
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

Related to Installer - Bug #35684: Filter "Applied catalog in x.y seconds" messages out of Puppet reportClosed

History

#1 Updated by The Foreman Bot about 2 months ago

  • Assignee set to Ewoud Kohl van Wijngaarden
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/9536 added

#2 Updated by Ewoud Kohl van Wijngaarden about 2 months ago

  • Related to Bug #35684: Filter "Applied catalog in x.y seconds" messages out of Puppet report added

#3 Updated by Ewoud Kohl van Wijngaarden about 2 months ago

  • Target version set to 3.5.0

#4 Updated by Ewoud Kohl van Wijngaarden about 2 months ago

  • Target version deleted (3.5.0)

This will be documented as a known issue and postponed to a later version.

#5 Updated by Ewoud Kohl van Wijngaarden about 1 month ago

  • Target version set to 3.5.1

#6 Updated by Ewoud Kohl van Wijngaarden about 1 month ago

  • Target version changed from 3.5.1 to 3.5.2

Also available in: Atom PDF