Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 2192937

Summary:	Puppet configuration reports without entries do not get an origin
Product:	Red Hat Satellite	Reporter:	Ewoud Kohl van Wijngaarden <ekohlvan>
Component:	Puppet	Assignee:	Ewoud Kohl van Wijngaarden <ekohlvan>
Status:	CLOSED DUPLICATE	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.13.0
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-04 15:22:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ewoud Kohl van Wijngaarden 2023-05-03 15:51:49 UTC

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.

Comment 1 Ewoud Kohl van Wijngaarden 2023-05-03 15:51:54 UTC

Created from redmine issue https://projects.theforeman.org/issues/35833

Comment 2 Bryan Kearney 2023-05-03 16:03:29 UTC

Upstream bug assigned to ekohlvan

Comment 3 Bryan Kearney 2023-05-03 16:03:31 UTC

Upstream bug assigned to ekohlvan

Comment 4 Brad Buckingham 2023-05-04 15:22:03 UTC

This bugzilla appears to be a clone from the upstream redmine (35833) and a duplicate of bug 2192939.  Since the description on 2192939 provides additional details on the scenarios, closing this one.  If this is incorrect, please do re-open with appropriate details.  Thanks!

*** This bug has been marked as a duplicate of bug 2192939 ***