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.
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:
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)
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