Project

General

Profile

Actions

Bug #27097

closed

foreman-proxy not launching because of 'uninitialized constant ForemanTasksCore::TaskLauncher'

Added by Sylvain Coutant about 5 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:

Description

Hello,

On a clean new 1.22 installation (foreman-installer over Ubuntu 18.04), foreman-proxy crashes with:

Jun 21 09:14:57 foreman.core.par1.stgi.io smart-proxy[4377]: /usr/lib/ruby/vendor_ruby/foreman_remote_execution_core.rb:75:in `<module:ForemanRemoteExecutionCore>': uninitialized constant ForemanTasksCore::TaskLauncher (NameError)
Jun 21 09:14:57 foreman.core.par1.stgi.io smart-proxy[4377]:         from /usr/lib/ruby/vendor_ruby/foreman_remote_execution_core.rb:3:in `<top (required)>'
Jun 21 09:14:57 foreman.core.par1.stgi.io smart-proxy[4377]:         from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
Jun 21 09:14:57 foreman.core.par1.stgi.io smart-proxy[4377]:         from /usr/lib/ruby/vendor_ruby/bundler_ext/runtime.rb:41:in `block in system_require'
Jun 21 09:14:57 foreman.core.par1.stgi.io smart-proxy[4377]:         from /usr/lib/ruby/vendor_ruby/bundler_ext/runtime.rb:37:in `each'
Jun 21 09:14:57 foreman.core.par1.stgi.io smart-proxy[4377]:         from /usr/lib/ruby/vendor_ruby/bundler_ext/runtime.rb:37:in `system_require'
Jun 21 09:14:57 foreman.core.par1.stgi.io smart-proxy[4377]:         from /usr/lib/ruby/vendor_ruby/bundler_ext.rb:19:in `block in system_require'
Jun 21 09:14:57 foreman.core.par1.stgi.io smart-proxy[4377]:         from /usr/lib/ruby/vendor_ruby/bundler_ext.rb:14:in `each'
Jun 21 09:14:57 foreman.core.par1.stgi.io smart-proxy[4377]:         from /usr/lib/ruby/vendor_ruby/bundler_ext.rb:14:in `system_require'
Jun 21 09:14:57 foreman.core.par1.stgi.io smart-proxy[4377]:         from /usr/share/foreman-proxy/lib/bundler_helper.rb:22:in `require_groups'
Jun 21 09:14:57 foreman.core.par1.stgi.io smart-proxy[4377]:         from /usr/share/foreman-proxy/lib/smart_proxy_main.rb:33:in `<top (required)>'
Jun 21 09:14:57 foreman.core.par1.stgi.io smart-proxy[4377]:         from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
Jun 21 09:14:57 foreman.core.par1.stgi.io smart-proxy[4377]:         from /usr/share/foreman-proxy/bin/smart-proxy:5:in `<main>'

I'm no Ruby expert, but from what I saw, foreman-tasks-core (0.2.5) does not implement some changes introduced by https://github.com/theforeman/foreman_remote_execution/commit/698e66a29f32fad93abbd396d59d6de05a3f11a3 => foreman_remote_execution_core (1.1.6).

Downgrading to foreman_remote_execution_core 1.1.3 from the 1.20 repo seems to solve the issue but I don't know which side effects it could have. The remote execution runs after this (I'm now facing script errors, it doesn't seem to be related).

NOTE: I also pinned ruby-concurrent package to 1.0.0 version (from official Ubuntu 16.04 Xenial repo) to 'solve' the Concurrent::Edge::Future issue (https://github.com/theforeman/foreman-packaging/pull/3438)
My current apt pin config is:

Package: ruby-concurrent
Pin: version 1.0.0*
Pin-Priority: 1001

Package: ruby-foreman-remote-execution-core
Pin: version 1.1.3*
Pin-Priority: 1001

*** LOCAL GEMS ***

algebrick (0.7.4)
ansi (1.5.0)
apipie-params (0.0.5)
bcrypt_pbkdf (1.0.0)
bigdecimal (default: 1.3.4)
bundler (1.16.1)
bundler_ext (0.4.1)
clamp (1.1.1)
cmath (default: 1.0.0)
concurrent-ruby (1.0.0)
csv (default: 1.0.0)
date (default: 1.0.0)
dbm (default: 1.0.0)
did_you_mean (1.2.0)
domain_name (0.5.20160216)
dynflow (1.1.6)
etc (default: 1.0.0)
facter (2.5.1)
fcntl (default: 1.0.0)
ffi (1.9.10)
fiddle (default: 1.0.0)
fileutils (default: 1.0.2)
foreman-tasks-core (0.2.6)
foreman_remote_execution_core (1.1.3)
gdbm (default: 2.0.0)
gssapi (1.2.0)
hashie (3.5.5)
highline (1.7.8)
http-cookie (1.0.2)
io-console (default: 0.4.6)
ipaddr (default: 1.2.0)
json (default: 2.1.0)
jwt (1.5.6)
kafo (3.0.0)
kafo_parsers (1.0.0)
kafo_wizards (0.0.1)
little-plugger (1.1.4)
logging (2.1.0.48)
mime-types (3.1)
mime-types-data (3.2015.1120)
minitest (5.10.3)
molinillo (0.6.4)
multi_json (1.12.1)
net-http-persistent (2.9.4)
net-scp (1.2.1)
net-ssh (4.2.0)
net-telnet (0.1.1)
netrc (0.11.0)
oj (3.4.0)
openssl (default: 2.1.1)
pg (0.19.0)
power_assert (0.2.7)
powerbar (1.0.18)
psych (default: 3.0.2)
rack (1.6.4)
rack-protection (1.5.3)
rake (12.3.1)
rb-inotify (0.9.7)
rbnacl (5.0.0)
rbnacl-libsodium (1.0.16)
rdoc (default: 6.0.1)
rest-client (2.0.2)
rkerberos (0.1.3)
rsec (0.4.2)
ruby-libvirt (0.7.0)
rubyipmi (0.10.0)
scanf (default: 1.0.0)
sdbm (default: 1.0.0)
sequel (5.6.0)
sinatra (1.4.8)
smart_proxy_ansible (3.0.0)
smart_proxy_dynflow (0.2.2)
smart_proxy_dynflow_core (0.2.2)
smart_proxy_remote_execution_ssh (0.2.1)
sqlite3 (1.3.13)
stringio (default: 0.0.1)
strscan (default: 1.0.0)
test-unit (3.2.5)
thor (0.19.4)
tilt (2.0.1)
unf (0.1.4)
unf_ext (0.0.7.4)
webrick (default: 1.4.2)
xmlrpc (0.3.0)
zlib (default: 1.0.0)
Actions #1

Updated by Adam Ruzicka over 3 years ago

  • Status changed from New to Closed

1.22 is EOL, this shouldn't be an issue on currently supported releases.

Actions

Also available in: Atom PDF