+++ This bug was initially created as a clone of Bug #2192939 +++

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.

— Additional comment from on 2023-05-03T16:03:34Z

Upstream bug assigned to ekohlvan@redhat.com

— Additional comment from on 2023-05-03T16:03:36Z

Upstream bug assigned to ekohlvan@redhat.com

— Additional comment from on 2023-05-04T15:22:03Z

• • • Bug 2192937 has been marked as a duplicate of this bug. ***

— Additional comment from on 2023-05-04T15:24:59Z

The referenced redmine (35684) is introduced in foreman 3.5 which is the upstream to Satellite 6.13; therefore, proposing this bugzilla for 6.13.z & 6.14.0.

Since the issue appears to be a regression in behavior, going to add Regression keyword. This will help ensure it is selected for 6.13.z. If this is incorrect, please feel free to update.

— Additional comment from on 2023-06-06T13:59:03Z

// Internal notes

The customer has escalated the linked case, I can see the upstream BZ is closed. Need ETA when a HOTFIX will be available, so that I can share the same with the customer.

— Additional comment from on 2023-06-14T14:17:55Z

Hi team,

The case is now escalated for little over week, could we please get an update?

Thank you.
Bety Skopova
Escalation Manager
CAP Experience Engineering
Red Hat

— Additional comment from on 2023-06-16T18:42:15Z

Adding sat-6.14.z+ based upon discussion at 6/07 re-triage.

— Additional comment from on 2023-06-16T18:43:54Z

Bety,

I just saw comment 6. Please be aware that Ewoud has been on PTO and unable to reply. I believe he should be returning next week and will be catching up.

— Additional comment from on 2023-06-19T08:28:22Z

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.

— Additional comment from on 2023-06-21T13:48:52Z

And https://github.com/theforeman/foreman-installer/commit/d1b65096a8ac8e25e5a3a1671c9157ea3b53541a is the upstream installer commit that reverts it for Foreman 3.7. That means it should be part of 6.14 already. Only needs a cherry pick for 6.13.

— Additional comment from on 2023-08-07T15:06:16Z

// @Ewoud Kohl van Wijngaarden, the customer has escalated the case twice, need fix for 6.13 ASAP.

— Additional comment from on 2023-08-07T20:15:55Z

// Escalation Team Note //

• The customer from 03522208 hit the escalation again asking for an status.
• I set some expectations about resolution and SLA/ETA for a bug, but they are not happy with the lack of update / progress.
• I am setting the Customer Escalation flag on this BZ for awareness.
• Based on the last update (Comment #10), it seems that it is not complicate to have the 6.13 fix. How is the status of the fix in this case?

–
Anderson Kaiser
Critical Situation Manager

— Additional comment from on 2023-08-08T09:20:41Z

I think I should have moved this to post so it would have been picked up.

— Additional comment from on 2023-08-08T12:20:37Z

(In reply to Anderson Kaiser from comment #12)
> // Escalation Team Note //
>
> - The customer from 03522208 hit the escalation again asking for an status.
> - I set some expectations about resolution and SLA/ETA for a bug, but they
> are not happy with the lack of update / progress.
> - I am setting the Customer Escalation flag on this BZ for awareness.
> - Based on the last update (Comment #10), it seems that it is not complicate
> to have the 6.13 fix. How is the status of the fix in this case?
>
> –
> Anderson Kaiser
> Critical Situation Manager

Hi Kaiser,

We do z-streams monthly on Satellite, and right now we are in the middle of 6.12.5, we do have planned for later this month one ASYNC for 6.13.z with a really small number of bug. I can bring this later to Program to see if we can include this in the ASYNC list.

For the moment, the best approach for this customer would be to ask for a hotfix, the hotfix request should be done at satellite-prio@redhat.com.

Regards,
Odilon Sousa

QE Tracker for https://issues.redhat.com/browse/SAT-22348
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2257314