Project

General

Profile

Actions
Copy link

Bug #32078

closed

smart_proxy_dynflow_core is not restarted after re-configuration

Added by Evgeni Golov about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
High
Assignee:
Evgeni Golov
Category:
Foreman modules
Target version:
Foreman - 2.3.5
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
https://github.com/theforeman/puppet-foreman_proxy/pull/653, https://github.com/theforeman/foreman-installer/pull/662, https://github.com/theforeman/puppet-foreman_proxy/pull/681, https://github.com/theforeman/foreman-installer/pull/688
Fixed in Releases:
Foreman - 2.3.5, Foreman - 2.4.0
Found in Releases:
Foreman - 2.3.3, Foreman - 2.4.0
Red Hat JIRA:

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 :(

Actions
Copy link

Also available in: Atom PDF