smart_proxy_dynflow_core is not restarted after re-configuration
during plugin testing we found out that sp_d_core is not restarted after a re-configuration by the installer, thus still running a wrong config (see https://community.theforeman.org/t/foreman-plugins-2-4-rpm-test-pipeline-1-failed/22742/).
The core (heh) of the problem is that we assumed that A~>B~>C in Puppet means that a change to A also will notify C, but that is not the case. (https://github.com/theforeman/puppet-foreman_proxy/blob/aeb026b6758f5b9752de2b579f931596d6de1311/manifests/plugin/dynflow.pp#L54-L71)
A wrongly configured dynflow_core after an upgrade essentially means no working tasks :(
#4 Updated by Evgeni Golov 7 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-foreman_proxy|763aba8f18e028548152d8a41bbafc142702c5e8.