Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Puppet
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: 6.15.0
Assignee: Ewoud Kohl van Wijngaarden
QA Contact: Gaurav Talreja
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: 2024-04-23 17:11 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2257314 2257327 (view as bug list)
Environment:
Last Closed: 2024-04-23 17:11:09 UTC
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-09-08 11:00:09 UTC
Red Hat Issue Tracker SAT-17550 0 None None None 2023-05-04 15:25:57 UTC
Red Hat Product Errata RHSA-2024:2010 0 None None None 2024-04-23 17:11:11 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.
Comment 15 Gaurav Talreja 2024-02-07 22:26:39 UTC 
Verified.

Tested on Satellite 6.15.0 Snap 9.0

Steps:
1. Enable puppet plugin on Satellite 6.15.0
2. Enable, and sync a few RH content and RH client repository
3. Register a host, install and configure puppet-agent on host
4. Run either "puppet agent --detailed-exitcodes" or "systemctl restart puppet", ensure its exit code is 0 (meaning no changes)
5. Navigate and expect a new config report generated for the host

Observation:
Here config report is created for host, and contains an origin Puppet as expected
Comment 18 errata-xmlrpc 2024-04-23 17:11:09 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.15.0 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2024:2010
Note You need to log in before you can comment on or make changes to this bug.