Bug 2257314

Summary:	Puppet reports without any messages don't get an origin
Product:	Red Hat Satellite	Reporter:	Odilon Sousa <osousa>
Component:	Puppet	Assignee:	Ewoud Kohl van Wijngaarden <ekohlvan>
Status:	CLOSED ERRATA	QA Contact:	Gaurav Talreja <gtalreja>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	6.13.0	CC:	akaiser, bskopova, gtalreja, nalfassi, osousa, pcreech, sadas, sussen
Target Milestone:	6.13.7	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman-installer-3.5.2.7-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2192939	Environment:
Last Closed:	2024-02-29 20:35:11 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:

Comment 3 Gaurav Talreja 2024-02-20 14:37:28 UTC

Verified.

Tested on Satellite 6.13.7 Snap 1.1

Steps:
1. Enable puppet plugin on Satellite 6.13.7
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 8 errata-xmlrpc 2024-02-29 20:35:11 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 (Moderate: Red Hat Satellite 6 security and bug fix update), 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:1061