di38rut
di38rut/sd9Pvr3L
I know the searching bug. It has nothing to do with that. It’s the status that is shown incorrectly on the host page.
For instance, I have a client host with docker updates pending. Trace status on the host page is O.K. That matches the status on the host:
[root@runner9 ~]# needs-restarting
Updating Subscription Management repositories.
[root@runner9 ~]# needs-restarting -s
Updating Subscription Management repositories.
[root@runner9 ~]# needs-restarting -r
Updating Subscription Management repositories.
No core libraries or services have been updated since boot-up.
Reboot should not be necessary.
[root@runner9 ~]# tracer
[root@runner9 ~]# lsof | fgrep -e DEL -e deleted | fgrep -v -e ' /var/lib/sss/mc/' -e ' /memfd:'
[root@runner9 ~]# katello-tracer-upload
Updating Subscription Management repositories.
Now I run the update. docker.service has been restarted during the update:
[root@runner9 ~]# systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; preset: d>
Active: active (running) since Tue 2024-07-23 07:09:23 CEST; 12s ago
TriggeredBy: ● docker.socket
…
Jul 23 07:09:23 runner9.example.com systemd[1]: Started Docker Application Containe>
On the client host everything looks O.K:
[root@runner9 ~]# needs-restarting
Updating Subscription Management repositories.
[root@runner9 ~]# needs-restarting -s
Updating Subscription Management repositories.
[root@runner9 ~]# needs-restarting -r
Updating Subscription Management repositories.
No core libraries or services have been updated since boot-up.
Reboot should not be necessary.
[root@runner9 ~]# tracer
[root@runner9 ~]# lsof | fgrep -e DEL -e deleted | fgrep -v -e ' /var/lib/sss/mc/' -e ' /memfd:'
[root@runner9 ~]#
However, the trace status in foreman on the client host page says that docker needs to be restarted.
[root@foreman8 ~]# hammer host traces list --host runner9.example.com
---------|-------------|-------------------------------|-------
TRACE ID | APPLICATION | HELPER | TYPE
---------|-------------|-------------------------------|-------
193703 | docker | sudo systemctl restart docker | daemon
---------|-------------|-------------------------------|-------
Even if I run katello-trace-upload on the client again:
[root@runner9 ~]# katello-tracer-upload
Updating Subscription Management repositories.
[root@runner9 ~]#
It still says to restart docker on foreman.
So no option to needs-restarting nor tracer says anything about a service restart. The service has been restarted during the update. Everything is fine on the client. Yet, foreman still thinks the service needs to be restarted.
Only after I restart docker.service again and run katello-tracer-upload, the trace status in foreman will be back to O.K. So it must be something else which determines why foreman thinks the service needs to be restarted…