Bug #32078
closed
smart_proxy_dynflow_core is not restarted after re-configuration
Description
Ohai,
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 :(
Updated by The Foreman Bot about 4 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/puppet-foreman_proxy/pull/653 added
Updated by Ewoud Kohl van Wijngaarden about 4 years ago
- Target version set to 2.4.0
Right now I'm targeting this at 2.4 but it should also be picked to 2.3.
Updated by Evgeni Golov about 4 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-foreman_proxy|763aba8f18e028548152d8a41bbafc142702c5e8.
Updated by The Foreman Bot about 4 years ago
- Pull request https://github.com/theforeman/foreman-installer/pull/662 added
Updated by Ewoud Kohl van Wijngaarden about 4 years ago
- Triaged changed from No to Yes
- Fixed in Releases 2.4.0 added
- Fixed in Releases deleted (
2.5.0)
Updated by Tomer Brisker almost 4 years ago
- Target version changed from 2.4.0 to 2.3.5
Updated by The Foreman Bot almost 4 years ago
- Pull request https://github.com/theforeman/puppet-foreman_proxy/pull/681 added
Updated by The Foreman Bot almost 4 years ago
- Pull request https://github.com/theforeman/foreman-installer/pull/688 added
Updated by Ewoud Kohl van Wijngaarden almost 4 years ago
- Fixed in Releases 2.3.5 added