Tracer wants to restart service after installation

After some updates, tracer incorrectly reports a necessary service restart even though the service has been restarted during update. Latest example: a new version of puppet-agent. I have updated it on all my content hosts and now all CentOS 7 hosts report the puppet needs to be restarted even though I verified on various hosts that puppet has been restarted. I don’t see this with all updates, only with some. Kind of defies the purpose of the whole tracer thing if it doesn’t correctly pick up a service restart during an update.

(CentOS 8 seems to report correctly)

I still haven’t figured out how tracer exactly decides whether a service needs to be restarted or not.

Foreman and Proxy versions:

katello-3.16.1-1.el7.noarch, foreman 2.1.4

Distribution and version:

CentOS 7.8.2003