Project

General

Profile

Actions
Copy link

Bug #28117

open

foreman-proxy failed - foreman_remote_execution

Added by Nicolas Boulanger almost 5 years ago. Updated over 4 years ago.

Status:
New
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Hello,

i cannot start foreman-proxy since the remote execution plugin installation with this command :

foreman-installer --no-enable-foreman-plugin-remote-execution --no-enable-foreman-proxy-plugin-remote-execution-ssh

Distributor ID: Debian
Description: Debian GNU/Linux 9.11 (stretch)
Release: 9.11
Codename: stretch

ii ruby-foreman-remote-execution-core 1.1.6-1 all Foreman remote execution - core bits
ii foreman 1.23.0-1 amd64 Systems management web interface
ii ruby-foreman-tasks 0.16.2-1 all Tasks management engine for Foreman.
ii ruby-foreman-tasks-core 0.2.5-1 all Foreman tasks - core bits
ii ruby-concurrent 1.0.0-3 all modern concurrency tools for Ruby

[ERROR 2019-10-23T08:45:46 verbose] Systemd start for foreman-proxy failed!
[ERROR 2019-10-23T08:45:46 verbose] journalctl log for foreman-proxy:
[ERROR 2019-10-23T08:45:46 verbose] -- Logs begin at Wed 2019-10-23 08:30:07 EDT, end at Wed 2019-10-23 08:45:46 EDT. --
[ERROR 2019-10-23T08:45:46 verbose] Oct 23 08:45:46 foreman.xxxx systemd1: Starting Foreman Proxy...
[ERROR 2019-10-23T08:45:46 verbose] Oct 23 08:45:46 foreman.xxxx smart-proxy5532: /usr/lib/ruby/vendor_ruby/foreman_remote_execution_core.rb:75:in `<module:ForemanRemoteExecutionCore>': uninitialized constant ForemanTasksCore::TaskLauncher (NameError)

could you take a look please ?
thanks

Actions
Copy link
 #1

Updated by Tomer Brisker almost 5 years ago

  • Project changed from Foreman to Foreman Remote Execution
  • Category deleted (Smart Proxy)
  • Found in Releases deleted (1.23.0)
Actions
Copy link
 #2

Updated by Adam Ruzicka almost 5 years ago

remote execution core 1.1.16 needs foreman tasks core >= 0.3.1, you have 0.2.5. Could you take a look if you could update it?

Actions
Copy link
 #3

Updated by Nicolas Boulanger almost 5 years ago

Adam Ruzicka wrote:

remote execution core 1.1.16 needs foreman tasks core >= 0.3.1, you have 0.2.5. Could you take a look if you could update it?

there is no update on foreman repo:
http://deb.theforeman.org/pool/stretch/nightly/r/ruby-foreman-tasks-core/

but i've update with gem
gem install -i /usr/share/rubygems-integration/all foreman-tasks-core -v 0.3.1

then smart-proxy does not start:
/usr/lib/ruby/vendor_ruby/foreman_remote_execution_core.rb:75:in `<module:ForemanRemoteExecutionCore>': uninitialized constant ForemanTasksCore::TaskLauncher (NameError)

gem version:
foreman-tasks-core (0.3.1)
foreman_remote_execution_core (1.1.6)

Actions
Copy link
 #4

Updated by Adam Ruzicka almost 5 years ago

It seems that debian packaging for foreman tasks core is blocked on concurrent ruby not playing nice with debian packaging. Until that is resolved, I'm afraid we cannot do much about it

Actions
Copy link
 #5

Updated by Elias Pereira over 4 years ago

Adam Ruzicka wrote:

It seems that debian packaging for foreman tasks core is blocked on concurrent ruby not playing nice with debian packaging. Until that is resolved, I'm afraid we cannot do much about it

Hello Adam, it looks like the concurrent ruby guys fixed this problem. Any idea when this problem will be fixed in the remote execution plugin?

Actions
Copy link

Also available in: Atom PDF