Bug #29281

Updated by Ewoud Kohl van Wijngaarden 7 months ago

When upgrading from Foreman 1.24 to 2.0, the dynflowd service is still running. I would expect that the foreman RPM makes sure the service is stopped since the unit file is no longer shipped.

Note it's not possible to stop a service after its unit file has been removed:
[root@pipeline-foreman-server-1-24-centos7 ~]# systemctl --no-reload disable --now dynflowd
Failed to execute operation: No such file or directory
[root@pipeline-foreman-server-1-24-centos7 ~]# systemctl status dynflowd
● dynflowd.service
Loaded: not-found (Reason: No such file or directory)
Active: active (running) since Fri 2020-03-06 14:52:43 UTC; 1h 17min ago
CGroup: /system.slice/dynflowd.service
├─20590 dynflow_executor_monitor
└─20596 dynflow_executor

It can also be seen that a foreman-tasks.service remains as a dangling symlink:
[root@pipeline-foreman-server-1-24-centos7 ~]# ls -l /etc/systemd/system/foreman-tasks.service
lrwxrwxrwx. 1 root root 40 Mar 6 14:52 /etc/systemd/system/foreman-tasks.service -> /usr/lib/systemd/system/dynflowd.service