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 2180761 - problems with webhooks are only logged to production.log, no failed task, no other notification
Summary: problems with webhooks are only logged to production.log, no failed task, no ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hooks and Webhooks
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.15.0
Assignee: Adam Ruzicka
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-22 08:24 UTC by Evgeni Golov
Modified: 2024-04-23 17:13 UTC (History)
4 users (show)

Fixed In Version: rubygem-foreman_webhooks-3.2.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-23 17:13:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 32368 0 Normal Closed When a webhook fails, I want to be somehow informed about that 2023-11-08 09:18:27 UTC
Red Hat Issue Tracker SAT-18426 0 None None None 2023-06-15 08:02:58 UTC
Red Hat Issue Tracker SAT-20982 0 None None None 2023-11-03 15:18:49 UTC
Red Hat Product Errata RHSA-2024:2010 0 None None None 2024-04-23 17:13:58 UTC

Description Evgeni Golov 2023-03-22 08:24:55 UTC 
Description of problem:
webhooks sometimes fail, but as an admin of a satellite I have no way to know about this without grepping /var/log/foreman/production.log

Version-Release number of selected component (if applicable):
any containing foreman_webhooks

How reproducible:
100%

Steps to Reproduce:
1. make a webhook fail
2. try to find out

Actual results:
only production.log has the data

Expected results:
either a failed task or a notification area entry or something that people can actually watch and react to

Additional info:
Comment 1 Brad Buckingham 2023-03-23 14:23:56 UTC 
Would you consider this an RFE or defect?
Comment 2 Evgeni Golov 2023-03-23 14:34:24 UTC 
I consider this a defect as it makes using/debugging the core functionality really hard.
Comment 3 Adam Ruzicka 2023-06-14 12:30:13 UTC 
Would you happen to have an example? What kind of failure are we talking about?
Comment 4 Evgeni Golov 2023-06-15 07:05:13 UTC 
I don't have an example at hand (but could generate you one if you want), but my memory says I had the two following failures where I wanted a more detailed info about:
1/ bad webhook url, so it would either run in a timeout or get a 404
2/ bad payload, which was rejected by the receiver with a 500 error (I guess technically it should have been a 422 - Unprocessable Entity, but the receiver I was using raised a 500)
Comment 6 Bryan Kearney 2023-11-07 16:02:30 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32368 has been resolved.
Comment 7 Peter Ondrejka 2023-11-27 15:25:16 UTC 
Verified in Satellite stream snap 38
Comment 10 errata-xmlrpc 2024-04-23 17:13:57 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.