Project

General

Profile

Actions

Bug #24857

closed

Systemd start for smart_proxy_dynflow_core failed! / `strict_err': Gem loading error: cannot load such file -- foreman_ansible_core (RuntimeError)

Added by Nicolas BOUCHARD about 6 years ago. Updated about 6 years ago.


Description

Hello Team,

I'm trying to deploy an ansible smart proxy with foreman 1.19 and CentOS 7.

I'm using foreman-installer with this options :
foreman-installer \
--enable-foreman-proxy-plugin-ansible \
--enable-foreman-proxy-plugin-remote-execution-ssh

Foreman Installer is reporting this error :

 [ERROR 2018-09-09T02:35:18 main]  /Stage[main]/Foreman_proxy::Plugin::Dynflow/Service[smart_proxy_dynflow_core]/ensure: change from 'stopped' to 'running' failed: Systemd start for smart_proxy_dynflow_core failed!
[ERROR 2018-09-09T02:35:18 main] journalctl log for smart_proxy_dynflow_core:
[ERROR 2018-09-09T02:35:18 main] -- Logs begin at Sat 2018-09-08 22:37:09 CEST, end at Sun 2018-09-09 02:35:18 CEST. --
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:16 nb-foreman-prox-01.home systemd[1]: Starting Foreman smart proxy dynflow core service...
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home smart_proxy_dynflow_core[22967]: /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext/output.rb:13:in `strict_err': Gem loading error: cannot load such file -- foreman_ansible_core (RuntimeError)
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home smart_proxy_dynflow_core[22967]: from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext/runtime.rb:46:in `rescue in block in system_require'
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home smart_proxy_dynflow_core[22967]: from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext/runtime.rb:39:in `block in system_require'
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home smart_proxy_dynflow_core[22967]: from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext/runtime.rb:37:in `each'
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home smart_proxy_dynflow_core[22967]: from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext/runtime.rb:37:in `system_require'
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home smart_proxy_dynflow_core[22967]: from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext.rb:19:in `block in system_require'
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home smart_proxy_dynflow_core[22967]: from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext.rb:14:in `each'
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home smart_proxy_dynflow_core[22967]: from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext.rb:14:in `system_require'
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home smart_proxy_dynflow_core[22967]: from /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.2.0/lib/smart_proxy_dynflow_core/bundler_helper.rb:22:in `require_groups'
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home smart_proxy_dynflow_core[22967]: from /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.2.0/lib/smart_proxy_dynflow_core/launcher.rb:29:in `load_settings!'
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home smart_proxy_dynflow_core[22967]: from /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.2.0/lib/smart_proxy_dynflow_core/launcher.rb:13:in `start'
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home smart_proxy_dynflow_core[22967]: from /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.2.0/lib/smart_proxy_dynflow_core/launcher.rb:9:in `launch!'
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home smart_proxy_dynflow_core[22967]: from /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.2.0/bin/smart_proxy_dynflow_core:32:in `<top (required)>'
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home smart_proxy_dynflow_core[22967]: from /usr/bin/smart_proxy_dynflow_core:22:in `load'
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home smart_proxy_dynflow_core[22967]: from /usr/bin/smart_proxy_dynflow_core:22:in `<main>'
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home systemd[1]: smart_proxy_dynflow_core.service: control process exited, code=exited status=1
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home systemd[1]: Failed to start Foreman smart proxy dynflow core service.
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home systemd[1]: Unit smart_proxy_dynflow_core.service entered failed state.
[ERROR 2018-09-09T02:35:18 main] Sep 09 02:35:18 nb-foreman-prox-01.home systemd[1]: smart_proxy_dynflow_core.service failed.

If I try to start the process manually, I have the same error :

# smart_proxy_dynflow_core
/opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext/output.rb:13:in `strict_err': Gem loading error: cannot load such file -- foreman_ansible_core (RuntimeError)
        from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext/runtime.rb:46:in `rescue in block in system_require'
        from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext/runtime.rb:39:in `block in system_require'
        from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext/runtime.rb:37:in `each'
        from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext/runtime.rb:37:in `system_require'
        from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext.rb:19:in `block in system_require'
        from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext.rb:14:in `each'
        from /opt/theforeman/tfm/root/usr/share/gems/gems/bundler_ext-0.4.1/lib/bundler_ext.rb:14:in `system_require'
        from /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.2.0/lib/smart_proxy_dynflow_core/bundler_helper.rb:22:in `require_groups'
        from /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.2.0/lib/smart_proxy_dynflow_core/launcher.rb:29:in `load_settings!'
        from /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.2.0/lib/smart_proxy_dynflow_core/launcher.rb:13:in `start'
        from /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.2.0/lib/smart_proxy_dynflow_core/launcher.rb:9:in `launch!'
        from /opt/theforeman/tfm/root/usr/share/gems/gems/smart_proxy_dynflow_core-0.2.0/bin/smart_proxy_dynflow_core:32:in `<top (required)>'
        from /usr/bin/smart_proxy_dynflow_core:22:in `load'
        from /usr/bin/smart_proxy_dynflow_core:22:in `<main>'

I have the following RPM :
rubygem-smart_proxy_ansible-2.0.3-1.fm1_19.el7.noarch
rubygem-smart_proxy_dynflow-0.2.0-1.el7.noarch
rubygem-smart_proxy_remote_execution_ssh-0.2.0-2.el7.noarch
tfm-rubygem-foreman_remote_execution_core-1.1.3-1.el7.noarch
tfm-rubygem-dynflow-1.1.0-1.el7.noarch
tfm-ror51-rubygem-rack-2.0.3-2.el7.centos.noarch
tfm-ror51-rubygem-rack-protection-2.0.0-2.el7.centos.noarch
tfm-rubygem-domain_name-0.5.20160310-2.el7.noarch
tfm-rubygem-apipie-params-0.0.5-2.el7.noarch
tfm-ror51-rubygem-mime-types-3.1-2.el7.centos.noarch
tfm-rubygem-net-ssh-4.0.1-4.el7.noarch
tfm-rubygem-sequel-5.7.1-1.el7.noarch
tfm-rubygem-algebrick-0.7.3-5.el7.noarch
tfm-rubygem-http-cookie-1.0.2-2.el7.noarch
tfm-ror51-rubygem-sqlite3-1.3.13-2.el7.centos.x86_64
tfm-ror51-rubygem-mustermann-1.0.1-2.el7.centos.noarch
tfm-rubygem-rest-client-2.0.1-2.el7.noarch
tfm-ror51-runtime-1.1-2.el7.centos.x86_64
tfm-ror51-rubygem-concurrent-ruby-1.0.5-4.el7.centos.noarch
tfm-rubygem-unf_ext-0.0.6-7.el7.x86_64
tfm-rubygem-foreman-tasks-core-0.2.5-1.fm1_18.el7.noarch
tfm-ror51-rubygem-tilt-2.0.8-2.el7.centos.noarch
tfm-ror51-rubygem-sinatra-2.0.0-2.el7.centos.noarch
tfm-rubygem-smart_proxy_dynflow_core-0.2.0-1.fm1_18.el7.noarch
tfm-runtime-4.0-3.el7.x86_64
tfm-rubygem-concurrent-ruby-edge-0.2.4-1.el7.noarch
tfm-rubygem-unf-0.1.3-6.el7.noarch
tfm-rubygem-netrc-0.11.0-2.el7.noarch
tfm-ror51-rubygem-multi_json-1.12.2-2.el7.centos.noarch
tfm-ror51-rubygem-mime-types-data-3.2016.0521-2.el7.centos.noarch
tfm-rubygem-bundler_ext-0.4.1-2.el7.noarch
foreman-release-1.19.0-1.el7.noarch
foreman-proxy-1.19.0-1.el7.noarch
foreman-installer-1.19.0-1.el7.noarch
foreman-release-scl-7-1.el7.noarch
foreman-selinux-1.19.0-1.el7.noarch
foreman-debug-1.19.0-1.el7.noarch
ansible-2.6.3-1.el7.noarch

CentOS version is : CentOS Linux release 7.5.1804 (Core)

BR,

Actions #1

Updated by Anonymous about 6 years ago

  • Project changed from Foreman to Packaging
  • Category set to RPMs
  • Found in Releases 1.19.0 added
  • Found in Releases deleted (1.19.1)
Actions #2

Updated by Nicolas BOUCHARD about 6 years ago

Manually installing package tfm-rubygem-foreman_ansible_core is resolving the issue:
yum install -y tfm-rubygem-foreman_ansible_core

Actions #3

Updated by Ewoud Kohl van Wijngaarden about 6 years ago

  • Description updated (diff)
Actions #4

Updated by Ewoud Kohl van Wijngaarden about 6 years ago

  • Description updated (diff)
Actions #5

Updated by The Foreman Bot about 6 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Ewoud Kohl van Wijngaarden
  • Pull request https://github.com/theforeman/foreman-packaging/pull/2993 added
Actions #6

Updated by Ewoud Kohl van Wijngaarden about 6 years ago

  • Found in Releases 1.18.2, 1.20.0 added
Actions #7

Updated by The Foreman Bot about 6 years ago

  • Pull request https://github.com/theforeman/foreman-packaging/pull/3004 added
Actions #8

Updated by The Foreman Bot about 6 years ago

  • Pull request https://github.com/theforeman/foreman-packaging/pull/3005 added
Actions #9

Updated by Ewoud Kohl van Wijngaarden about 6 years ago

  • Status changed from Ready For Testing to Closed
Actions #10

Updated by Ewoud Kohl van Wijngaarden about 6 years ago

  • Fixed in Releases 1.18.3, 1.19.1, 1.20.0 added

Since a plugin is released async the Fixed in Releases is technically not 100% correct, but close enough. This is just to indicate it's been fixed in multiple branches.

Actions

Also available in: Atom PDF