Bug 2192939 - Puppet reports without any messages don't get an origin
Summary: Puppet reports without any messages don't get an origin
Keywords:
Status: POST
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Puppet
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: Ewoud Kohl van Wijngaarden
QA Contact: Satellite QE Team
URL:
Whiteboard:
: 2192937 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-03 15:56 UTC by Ewoud Kohl van Wijngaarden
Modified: 2023-08-08 12:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35833 0 Normal Ready For Testing Puppet configuration reports without entries do not get an origin 2023-05-03 15:56:44 UTC
Red Hat Issue Tracker SAT-17550 0 None None None 2023-05-04 15:25:57 UTC

Description Ewoud Kohl van Wijngaarden 2023-05-03 15:56:45 UTC 
Description of problem:

Since https://projects.theforeman.org/issues/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.

Version-Release number of selected component (if applicable):

Foreman 3.4.0, so Satellite 6.13.0

How reproducible:

Always

Steps to Reproduce:

1. Run puppet agent -t --detailed-exitcodes and ensure its exit code is 0 (meaning no changes)
2. Look for Puppet reports on the host
3. Expect to find the new report with origin Puppet

Actual results:

A report is created, but without an origin

Expected results:

The origin Puppet is set.

Additional info:

The Puppet origin is derived from the messages, but if there are no messages then it can't.
Comment 1 Bryan Kearney 2023-05-03 16:03:34 UTC 
Upstream bug assigned to ekohlvan
Comment 2 Bryan Kearney 2023-05-03 16:03:36 UTC 
Upstream bug assigned to ekohlvan
Comment 3 Brad Buckingham 2023-05-04 15:22:03 UTC 
*** Bug 2192937 has been marked as a duplicate of this bug. ***
Comment 9 Ewoud Kohl van Wijngaarden 2023-06-19 08:28:22 UTC 
I've been thinking about this and it's probably best to revert the problematic commit in the short term so I've opened https://github.com/theforeman/puppet-puppetserver_foreman/pull/29 for now.
Note You need to log in before you can comment on or make changes to this bug.