Task Cleanup broken after Upgrade from 1.22/3.12 to 2.0/3.15

Support
21

We don’t have foreman-maintain. It seems it not supported on Debian/Ubuntu: Is foreman-maintain supported on Ubuntu?

22

You really don’t need foreman-maintain. foreman-maintain service is just a thin wrapper around systemctl restart, but executes it sequentially in some order. As long as you know the right service names, there is really no reason to. It can also be significantly faster to let systemctl restart things in parallel.

23

So systemctl restart foreman should be enough ?
Following process welle restarted after systemctl restart foreman:

foreman   8126     1 26 11:57 ?        00:00:17 ruby2.5 /usr/share/foreman/vendor/ruby/2.5.0/bin/sidekiq -e production -r /usr/share/foreman/extras/dynflow-sidekiq.rb -C /etc/foreman/dynflow/orchestrator.yml
foreman   8161     1 43 11:58 ?        00:00:15 puma 4.3.5 (tcp://0.0.0.0:3000) [foreman]
foreman   8213  8161  0 11:58 ?        00:00:00 puma: cluster worker 0: 8161 [foreman]
foreman   8215  8161  0 11:58 ?        00:00:00 puma: cluster worker 1: 8161 [foreman]
foreman   8271     1  0 11:58 ?        00:00:00 /usr/bin/ruby /usr/bin/bundle exec sidekiq -e production -r /usr/share/foreman/extras/dynflow-sidekiq.rb -C /etc/foreman/dynflow/worker.yml

Is there something else to restart to fix my foreman-tasks issue ?

24

So there are a few services. foreman.service is the web process. There are also some dynflow workers which you also need to restart. Also remember that foreman-proxy needs to restart as well. So in the end, systemctl restart foreman foreman-proxy dynflow*

25

When I restart foreman with systemd its already restart following process:

  • PUMA
  • dynflow orchestrator
  • dynflow worker
    So not only puma but dynflow was restarted too.