Problem:
Every job invocation (remote execution) triggers a host_updated
webhook event, even though the host is not actually updated. This creates a lot of unnecessary processing and log chatter.
2025-02-03T00:42:30 [I|app|2b782497] ForemanWebhooks::EventSubscriber: actions.remote_execution.run_hosts_job_run_script_running.event.foreman event received
2025-02-03T00:42:30 [I|app|2b782497] ForemanWebhooks::EventSubscriber: actions.remote_execution.run_hosts_job_running.event.foreman event received
...
2025-02-03T00:44:29 [I|bac|2b782497] Event delivered by request 2378b799-9d0b-497f-aae1-353f98c995fd
2025-02-03T00:44:29 [I|app|2b782497] ForemanWebhooks::EventSubscriber: host_updated.event.foreman event received
How can i prevent the host_updated
webhook from triggering on job invocations?
Or can I somehow detect in my webhook template that it is not triggered by an actual host update?
Expected outcome:
host_updated
webhook should only be triggered on an actual update on the host.
Foreman and Proxy versions:
3.13
Foreman and Proxy plugin versions:
3.13
Distribution and version:
RHEL 9.5