Plugins » Foreman Remote Execution

Looks like downgrading tfm-rubygem-smart_proxy_dynflow_core.noarch to version 0.1.7 solves it.

Sorry, forgot to wrap...

Dec 06 12:24:44 example.com smart_proxy_dynflow_core24600: /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.1.8/lib/smart_proxy_dynflow_core.rb:13:in `<top (required)>': undefined method `silent_dead_letter_matchers' for ForemanTasksCore:Module (NoMethodError)
Dec 06 12:24:44 example.com smart_proxy_dynflow_core24600: from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require'
Dec 06 12:24:44 example.com smart_proxy_dynflow_core24600: from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require'
Dec 06 12:24:44 example.com smart_proxy_dynflow_core24600: from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext/runtime.rb:41:in `block in system_require'
Dec 06 12:24:44 example.com smart_proxy_dynflow_core24600: from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext/runtime.rb:37:in `each'
Dec 06 12:24:44 example.com smart_proxy_dynflow_core24600: from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext/runtime.rb:37:in `system_require'
Dec 06 12:24:44 example.com smart_proxy_dynflow_core24600: from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext.rb:19:in `block in system_require'
Dec 06 12:24:44 example.com smart_proxy_dynflow_core24600: from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext.rb:14:in `each'
Dec 06 12:24:44 example.com smart_proxy_dynflow_core24600: from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext.rb:14:in `system_require'
Dec 06 12:24:44 example.com smart_proxy_dynflow_core24600: from /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.1.8/lib/smart_proxy_dynflow_core/bundler_helper.rb:22:in `require_groups'
Dec 06 12:24:44 example.com smart_proxy_dynflow_core24600: from /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.1.8/lib/smart_proxy_dynflow_core/launcher.rb:27:in `load_settings!'
Dec 06 12:24:44 example.com smart_proxy_dynflow_core24600: from /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.1.8/lib/smart_proxy_dynflow_core/launcher.rb:13:in `start'
Dec 06 12:24:44 example.com smart_proxy_dynflow_core24600: from /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.1.8/lib/smart_proxy_dynflow_core/launcher.rb:9:in `launch!'
Dec 06 12:24:44 example.com smart_proxy_dynflow_core24600: from /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.1.8/bin/smart_proxy_dynflow_core:32:in `<top (required)>'
Dec 06 12:24:44 example.com smart_proxy_dynflow_core24600: from /usr/bin/smart_proxy_dynflow_core:23:in `load'
Dec 06 12:24:44 example.com smart_proxy_dynflow_core24600: from /usr/bin/smart_proxy_dynflow_core:23:in `<main>'
Dec 06 12:24:44 example.com systemd1: smart_proxy_dynflow_core.service: control process exited, code=exited status=1
Dec 06 12:24:44 example.com systemd1: Unit smart_proxy_dynflow_core.service entered failed state.
Dec 06 12:24:44 example.com systemd1: smart_proxy_dynflow_core.service failed.

Justin Sherrill wrote:

Moving to remote execution, doesn't seem related to katello.

I'm hitting the same problem after updating Katello to 3.5 and Foreman to 1.16.

rgds,
Arsène

Apparently we have wrongly set dependencies. Until this is fixed, please remove the line¹ which causes the error or downgrade smart_proxy_dynflow_core to an earlier version

[1] - /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.1.8/lib/smart_proxy_dynflow_core.rb:13

As Adam mentioned, the problem is in packaging, where we got stuck on coordination of changes between the foreman core and tasks. https://github.com/theforeman/foreman-packaging/pull/1549#issuecomment-350983953

The tasks release reqiired is sent https://github.com/theforeman/foreman-packaging/pull/1985, after that, we should be able also to push new rex version to 1.16