Issue starting foreman-proxy service

Support
,
1

Hello guys,

lately after os update " yum update -y " i have having trouble starting foreman-proxy service

Have tried looking for error but don’t find anything in logs except for “ERROR – : Error during startup, terminating. uninitialized constant Dynflow” in /var/log/foreman-proxy/proxy.log, can you please guide be where can i look for error to resolve this.

have uploaded the debug file at http://debugs.theforeman.org/foreman-debug-L66aw.tar.xz

OS: CentOS Linux release 7.4.1708
FOREMAN: 1.16.1
katello : 3.5.1
FOREMAN-PROXY: foreman-proxy-1.16.1
tfm-rubygem-smart_proxy_dynflow_core-0.1.7-1.fm1_16.el7.noarch
tfm-rubygem-dynflow-0.8.34-1.el7.noarch
rubygem-smart_proxy_dynflow-0.1.7-1.el7.noarch

2

@Dmitri_Dolguikh @iNecas @aruzicka - Any ideas?

3

Looking at the log it seems foreman-tasks-core gets loaded as a dependency of smart_proxy_ansible before dynflow is loaded and it fails because of it.

/usr/share/foreman-proxy/lib/launcher.rb:65:in `instance_eval'
/usr/local/share/gems/gems/foreman-tasks-core-0.2.4/lib/foreman_tasks_core/ticker.rb:1:in `<top (required)>'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/share/gems/gems/foreman-tasks-core-0.2.4/lib/foreman_tasks_core.rb:6:in `<top (required)>'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:135:in `require'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:135:in `rescue in require'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:144:in `require'
/usr/share/gems/gems/smart_proxy_ansible-2.0.2/lib/foreman_ansible_core.rb:2:in `<top (required)>'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/share/gems/gems/smart_proxy_ansible-2.0.2/lib/smart_proxy_ansible/api.rb:1:in `<top (required)>'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
(eval):1:in `block (2 levels) in https_app'
/usr/share/foreman-proxy/lib/launcher.rb:65:in `instance_eval'
/usr/share/foreman-proxy/lib/launcher.rb:65:in `block (2 levels) in https_app'
/usr/share/foreman-proxy/lib/launcher.rb:65:in `each'
/usr/share/foreman-proxy/lib/launcher.rb:65:in `block in https_app'
/usr/share/gems/gems/rack-1.6.4/lib/rack/builder.rb:55:in `instance_eval'
/usr/share/gems/gems/rack-1.6.4/lib/rack/builder.rb:55:in `initialize'
/usr/share/foreman-proxy/lib/launcher.rb:64:in `new'
/usr/share/foreman-proxy/lib/launcher.rb:64:in `https_app'
/usr/share/foreman-proxy/lib/launcher.rb:156:in `launch'
/usr/share/foreman-proxy/bin/smart-proxy:6:in `<main>'

CC @dLobatog

1 Like
4

Hi there,

any ideas how to fix this or work around this issue?

The setup is currently on those versions:

OS: Centos 7.x
Foreman: 1.20.1
Foreman-proxy: 1.20.1