Bug 2257327

Summary: Puppet reports without any messages don't get an origin
Product: Red Hat Satellite Reporter: Odilon Sousa <osousa>
Component: PuppetAssignee: Ewoud Kohl van Wijngaarden <ekohlvan>
Status: CLOSED ERRATA QA Contact: Gaurav Talreja <gtalreja>
Severity: unspecified Docs Contact:
Priority: high    
Version: 6.13.0CC: akaiser, bskopova, ekohlvan, gtalreja, nalfassi, osousa, sadas, sussen
Target Milestone: 6.14.2Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-installer-3.7.0.7-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2192939 Environment:
Last Closed: 2024-02-13 14:43:36 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 8 Gaurav Talreja 2024-02-02 18:26:17 UTC 
ah, gotcha, I think we're good to verify it then, Thanks for confirming it. 

"systemctl restart puppet" always triggers a run and generate a config report which it contains a Puppet origin correctly.

Verified on Satellite 6.14.2 Snap 2.0
Comment 13 errata-xmlrpc 2024-02-13 14:43:36 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.14.2 Async Security 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:0797