Project

General

Profile

Actions

Bug #26788

closed

Unable to upgrade from 1.21.1 to 1.22.x and to 1.23.X with foreman-remote-execution installed

Added by Elias Pereira almost 5 years ago. Updated almost 4 years ago.

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

Description

Hello,

I configured self-signed certificates for the foreman webgui. For a possible smart-proxy bug against remote_execution (https://projects.theforeman.org/issues/26684?issue_count=203&issue_position=1&next_issue_id=26671), in which I normally run the command, but the return returns a certificate error, I tried to upgrade to version 1.22 for a hope that would correct the bug/error. :(

Distro: Debian 9.9

After changing the apt and trying to execute the command:

apt-get --only-upgrade install ruby\* foreman\*

The following information may help to resolve the situation:

The following packages have unmet dependencies:
foreman-compute : Depends: foreman (= 1.21.3-1) but 1.22.0~rc1-1 is to be installed
E: Unable to correct problems, you have held broken packages.

  1. apt list --upgradable
    Listing... Done
    foreman/stretch 1.22.0~rc1-1 amd64 [upgradable from: 1.21.3-1]
    foreman-cli/stretch 1.22.0~rc1-1 all [upgradable from: 1.21.3-1]
    foreman-debug/stretch 1.22.0~rc1-1 all [upgradable from: 1.21.3-1]
    foreman-ec2/stretch 1.22.0~rc1-1 all [upgradable from: 1.21.3-1]
    foreman-installer/stretch 1.22.0~rc1-1 all [upgradable from: 1.21.3-1]
    foreman-libvirt/stretch 1.22.0~rc1-1 all [upgradable from: 1.21.3-1]
    foreman-postgresql/stretch 1.22.0~rc1-1 all [upgradable from: 1.21.3-1]
    foreman-proxy/stretch 1.22.0~rc1-1 all [upgradable from: 1.21.3-1]
    ruby-foreman-docker/plugins 4.1.1-1 all [upgradable from: 4.1.0-1]
    ruby-foreman-remote-execution/plugins 1.7.1-1 all [upgradable from: 1.7.0-1]
    ruby-foreman-remote-execution-core/stretch 1.1.6-1 all [upgradable from: 1.1.3-1]
    ruby-foreman-tasks/plugins 0.15.1-1 all [upgradable from: 0.14.5-2]
    ruby-hammer-cli/stretch 0.17.0-1 all [upgradable from: 0.16.0-1]
    ruby-hammer-cli-foreman/stretch 0.17.0-1 all [upgradable from: 0.16.0-1]
    ruby-kafo/stretch 3.0.0-1 all [upgradable from: 2.1.0-1]
    ruby-smart-proxy-remote-execution-ssh/plugins 0.2.1-1 all [upgradable from: 0.2.0-2]

Após isso tentei fazer um full-upgrade:

apt full-upgrade

return the errors:

dpkg: error processing package foreman-proxy (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of ruby-smart-proxy-remote-execution-ssh:
ruby-smart-proxy-remote-execution-ssh depends on foreman-proxy (>= 1.11.0~rc3); however:
Package foreman-proxy is not configured yet.

dpkg: error processing package ruby-smart-proxy-remote-execution-ssh (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
foreman-proxy
ruby-smart-proxy-remote-execution-ssh

syslog:

May 13 11:30:14 puppet systemd1: Reloading.
May 13 11:30:14 puppet systemd1: apt-daily.timer: Adding 2h 37min 17.026763s random time.
May 13 11:30:14 puppet systemd1: anacron.timer: Adding 4min 19.682345s random time.
May 13 11:30:14 puppet systemd1: Reloading.
May 13 11:30:14 puppet systemd1: apt-daily.timer: Adding 4h 29min 814.990ms random time.
May 13 11:30:14 puppet systemd1: anacron.timer: Adding 4min 37.850826s random time.
May 13 11:30:14 puppet systemd1: Starting Foreman Proxy...
May 13 11:30:15 puppet smart-proxy22313: /usr/lib/ruby/vendor_ruby/foreman_remote_execution_core.rb:75:in `<module:ForemanRemoteExecutionCore>': uninitialized constant ForemanTasksCore::TaskLauncher (NameError)
May 13 11:30:15 puppet smart-proxy22313: #011from /usr/lib/ruby/vendor_ruby/foreman_remote_execution_core.rb:3:in `<top (required)>'
May 13 11:30:15 puppet smart-proxy22313: #011from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
May 13 11:30:15 puppet smart-proxy22313: #011from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
May 13 11:30:15 puppet smart-proxy22313: #011from /usr/lib/ruby/vendor_ruby/bundler_ext/runtime.rb:41:in `block in system_require'
May 13 11:30:15 puppet smart-proxy22313: #011from /usr/lib/ruby/vendor_ruby/bundler_ext/runtime.rb:37:in `each'
May 13 11:30:15 puppet smart-proxy22313: #011from /usr/lib/ruby/vendor_ruby/bundler_ext/runtime.rb:37:in `system_require'
May 13 11:30:15 puppet smart-proxy22313: #011from /usr/lib/ruby/vendor_ruby/bundler_ext.rb:19:in `block in system_require'
May 13 11:30:15 puppet smart-proxy22313: #011from /usr/lib/ruby/vendor_ruby/bundler_ext.rb:14:in `each'
May 13 11:30:15 puppet smart-proxy22313: #011from /usr/lib/ruby/vendor_ruby/bundler_ext.rb:14:in `system_require'
May 13 11:30:15 puppet smart-proxy22313: #011from /usr/share/foreman-proxy/lib/bundler_helper.rb:22:in `require_groups'
May 13 11:30:15 puppet smart-proxy22313: #011from /usr/share/foreman-proxy/lib/smart_proxy_main.rb:33:in `<top (required)>'
May 13 11:30:15 puppet smart-proxy22313: #011from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
May 13 11:30:15 puppet smart-proxy22313: #011from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
May 13 11:30:15 puppet smart-proxy22313: #011from /usr/share/foreman-proxy/bin/smart-proxy:5:in `<main>'
May 13 11:30:15 puppet systemd1: foreman-proxy.service: Main process exited, code=exited, status=1/FAILURE
May 13 11:30:15 puppet systemd1: Failed to start Foreman Proxy.
May 13 11:30:15 puppet systemd1: foreman-proxy.service: Unit entered failed state.
May 13 11:30:15 puppet systemd1: foreman-proxy.service: Failed with result 'exit-code'.
May 13 11:30:15 puppet systemd1: Reloading.
May 13 11:30:16 puppet systemd1: apt-daily.timer: Adding 2h 3min 6.067282s random time.
May 13 11:30:16 puppet systemd1: anacron.timer: Adding 4min 37.487437s random time.
May 13 11:30:16 puppet systemd1: Reloading.
May 13 11:30:16 puppet systemd1: apt-daily.timer: Adding 8h 27min 4.633184s random time.
May 13 11:30:16 puppet systemd1: anacron.timer: Adding 4min 10.770095s random time.
May 13 11:30:16 puppet systemd1: Starting Foreman Proxy...
May 13 11:30:16 puppet smart-proxy22440: /usr/lib/ruby/vendor_ruby/foreman_remote_execution_core.rb:75:in `<module:ForemanRemoteExecutionCore>': uninitialized constant ForemanTasksCore::TaskLauncher (NameError)
May 13 11:30:16 puppet smart-proxy22440: #011from /usr/lib/ruby/vendor_ruby/foreman_remote_execution_core.rb:3:in `<top (required)>'
May 13 11:30:16 puppet smart-proxy22440: #011from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
May 13 11:30:16 puppet smart-proxy22440: #011from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
May 13 11:30:16 puppet smart-proxy22440: #011from /usr/lib/ruby/vendor_ruby/bundler_ext/runtime.rb:41:in `block in system_require'
May 13 11:30:16 puppet smart-proxy22440: #011from /usr/lib/ruby/vendor_ruby/bundler_ext/runtime.rb:37:in `each'
May 13 11:30:16 puppet smart-proxy22440: #011from /usr/lib/ruby/vendor_ruby/bundler_ext/runtime.rb:37:in `system_require'
May 13 11:30:16 puppet smart-proxy22440: #011from /usr/lib/ruby/vendor_ruby/bundler_ext.rb:19:in `block in system_require'
May 13 11:30:16 puppet smart-proxy22440: #011from /usr/lib/ruby/vendor_ruby/bundler_ext.rb:14:in `each'
May 13 11:30:16 puppet smart-proxy22440: #011from /usr/lib/ruby/vendor_ruby/bundler_ext.rb:14:in `system_require'
May 13 11:30:16 puppet smart-proxy22440: #011from /usr/share/foreman-proxy/lib/bundler_helper.rb:22:in `require_groups'
May 13 11:30:16 puppet smart-proxy22440: #011from /usr/share/foreman-proxy/lib/smart_proxy_main.rb:33:in `<top (required)>'
May 13 11:30:16 puppet smart-proxy22440: #011from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
May 13 11:30:16 puppet smart-proxy22440: #011from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
May 13 11:30:16 puppet smart-proxy22440: #011from /usr/share/foreman-proxy/bin/smart-proxy:5:in `<main>'
May 13 11:30:16 puppet systemd1: foreman-proxy.service: Main process exited, code=exited, status=1/FAILURE
May 13 11:30:16 puppet systemd1: Failed to start Foreman Proxy.
May 13 11:30:16 puppet systemd1: foreman-proxy.service: Unit entered failed state.
May 13 11:30:16 puppet systemd1: foreman-proxy.service: Failed with result 'exit-code'.

Thanks in advance for the help!


Related issues 1 (0 open1 closed)

Has duplicate Foreman - Bug #27860: Ubuntu/Deb smart proxy not loading correct ruby modulesDuplicateActions
Actions #1

Updated by Elias Pereira almost 5 years ago

  • Subject changed from Unable to upgrade from 1.21.1 to 1.22.x to Unable to upgrade from 1.21.1 to 1.22.x with foreman-remote-execution installed
Actions #2

Updated by Anonymous almost 5 years ago

  • Priority changed from High to Normal

could you dpkg --purge foreman-compute and then do the apt upgrade again?

Actions #3

Updated by Elias Pereira almost 5 years ago

Michael Moll wrote:

could you dpkg --purge foreman-compute and then do the apt upgrade again?

The same problem occurs.

Actions #4

Updated by Anonymous almost 5 years ago

just to get sure, which problem is still the same? The same that was happening in 1.21?

Actions #5

Updated by Elias Pereira almost 5 years ago

Michael Moll wrote:

just to get sure, which problem is still the same? The same that was happening in 1.21?

No. It is the same problem when upgrading from 1.21.1 to 1.22, as it is in the title.

The other problem is regarding the self-signed certificate.

Actions #6

Updated by Anonymous almost 5 years ago

https://github.com/theforeman/foreman-packaging/pull/3438 then, I guess... Which is waiting for me to fix that concurrent/ concurrent-edge stuff...

Actions #7

Updated by Elias Pereira almost 5 years ago

Michael Moll wrote:

https://github.com/theforeman/foreman-packaging/pull/3438 then, I guess... Which is waiting for me to fix that concurrent/ concurrent-edge stuff...

Okay. If I install the ruby-concurrent >= 1.1 version fixes or do you need to fix something else?

Actions #8

Updated by Elias Pereira almost 5 years ago

Michael Moll wrote:

https://github.com/theforeman/foreman-packaging/pull/3438 then, I guess... Which is waiting for me to fix that concurrent/ concurrent-edge stuff...

Does this package fix it?

https://github.com/ruby-concurrency/concurrent-ruby

Actions #9

Updated by Anonymous almost 5 years ago

It's about the DEB packaging.

Actions #10

Updated by Elias Pereira almost 5 years ago

Michael Moll wrote:

It's about the DEB packaging.

OK. Should not have a DEB package in version 1.1.x.

Do you have any idea when this package will be available?

Actions #11

Updated by Mauro Saderi over 4 years ago

Same issue happens with a fresh installation on Ubuntu 16.04

foreman-installer -v \
--enable-foreman-plugin-tasks \
--enable-foreman-plugin-templates \
--enable-foreman-plugin-remote-execution \
--enable-foreman-proxy-plugin-remote-execution-ssh \
--enable-foreman-proxy-plugin-dynflow

Installer reports error:

[ERROR 2019-07-19T07:27:22 verbose] /Service[foreman-proxy]: Failed to call refresh: Systemd restart for foreman-proxy failed!
[ERROR 2019-07-19T07:27:22 verbose] journalctl log for foreman-proxy:
[ERROR 2019-07-19T07:27:22 verbose] -- Logs begin at Fri 2019-07-19 07:11:33 UTC, end at Fri 2019-07-19 07:27:22 UTC. --
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:21 puppet-master systemd1: Stopping Foreman Proxy...
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:21 puppet-master systemd1: Stopped Foreman Proxy.
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:21 puppet-master systemd1: Starting Foreman Proxy...
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: /usr/lib/ruby/vendor_ruby/foreman_remote_execution_core.rb:75:in `<module:ForemanRemoteExecutionCore>': uninitialized constant ForemanTasksCore::TaskLauncher (NameError)
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/vendor_ruby/foreman_remote_execution_core.rb:3:in `<top (required)>'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/vendor_ruby/bundler_ext/runtime.rb:41:in `block in system_require'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/vendor_ruby/bundler_ext/runtime.rb:37:in `each'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/vendor_ruby/bundler_ext/runtime.rb:37:in `system_require'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/vendor_ruby/bundler_ext.rb:19:in `block in system_require'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/vendor_ruby/bundler_ext.rb:14:in `each'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/vendor_ruby/bundler_ext.rb:14:in `system_require'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/share/foreman-proxy/lib/bundler_helper.rb:22:in `require_groups'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/share/foreman-proxy/lib/smart_proxy_main.rb:33:in `<top (required)>'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/share/foreman-proxy/bin/smart-proxy:5:in `<main>'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master systemd1: foreman-proxy.service: Main process exited, code=exited, status=1/FAILURE
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master systemd1: Failed to start Foreman Proxy.
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master systemd1: foreman-proxy.service: Unit entered failed state.
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master systemd1: foreman-proxy.service: Failed with result 'exit-code'.

Actions #12

Updated by Elias Pereira over 4 years ago

Mauro Saderi wrote:

Same issue happens with a fresh installation on Ubuntu 16.04

[...]

Installer reports error:

[ERROR 2019-07-19T07:27:22 verbose] /Service[foreman-proxy]: Failed to call refresh: Systemd restart for foreman-proxy failed!
[ERROR 2019-07-19T07:27:22 verbose] journalctl log for foreman-proxy:
[ERROR 2019-07-19T07:27:22 verbose] -- Logs begin at Fri 2019-07-19 07:11:33 UTC, end at Fri 2019-07-19 07:27:22 UTC. --
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:21 puppet-master systemd1: Stopping Foreman Proxy...
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:21 puppet-master systemd1: Stopped Foreman Proxy.
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:21 puppet-master systemd1: Starting Foreman Proxy...
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: /usr/lib/ruby/vendor_ruby/foreman_remote_execution_core.rb:75:in `<module:ForemanRemoteExecutionCore>': uninitialized constant ForemanTasksCore::TaskLauncher (NameError)
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/vendor_ruby/foreman_remote_execution_core.rb:3:in `<top (required)>'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/vendor_ruby/bundler_ext/runtime.rb:41:in `block in system_require'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/vendor_ruby/bundler_ext/runtime.rb:37:in `each'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/vendor_ruby/bundler_ext/runtime.rb:37:in `system_require'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/vendor_ruby/bundler_ext.rb:19:in `block in system_require'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/vendor_ruby/bundler_ext.rb:14:in `each'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/vendor_ruby/bundler_ext.rb:14:in `system_require'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/share/foreman-proxy/lib/bundler_helper.rb:22:in `require_groups'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/share/foreman-proxy/lib/smart_proxy_main.rb:33:in `<top (required)>'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master smart-proxy3319: from /usr/share/foreman-proxy/bin/smart-proxy:5:in `<main>'
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master systemd1: foreman-proxy.service: Main process exited, code=exited, status=1/FAILURE
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master systemd1: Failed to start Foreman Proxy.
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master systemd1: foreman-proxy.service: Unit entered failed state.
[ERROR 2019-07-19T07:27:22 verbose] Jul 19 07:27:22 puppet-master systemd1: foreman-proxy.service: Failed with result 'exit-code'.

Hello Mauro,

Have you had any progress with your problem?

Actions #13

Updated by Anonymous over 4 years ago

  • Has duplicate Bug #27860: Ubuntu/Deb smart proxy not loading correct ruby modules added
Actions #14

Updated by Elias Pereira over 4 years ago

  • Subject changed from Unable to upgrade from 1.21.1 to 1.22.x with foreman-remote-execution installed to Unable to upgrade from 1.21.1 to 1.22.x and to 1.23.X with foreman-remote-execution installed
Actions #15

Updated by Elias Pereira over 4 years ago

Any news about this bug?

Actions #16

Updated by Nicolas Odermatt over 4 years ago

I ran into this problem too trying to update Foreman 1.21.3 to 1.22.x. Even though I don't have remote execution installed. In my case its the docker plugin that also relies on foreman-compute. Since I didn't use the docker plugin anymore, I decided to remove it from my system; follow the instructions carefully: https://github.com/theforeman/foreman_docker

Afterwards I followed the Foreman upgrade instructions and was able to run the foreman-installer successfully.

Note: The foreman-compute ist still at the previous version. I don't know why though my guess is that I currently don't use any compute resources. Maybe the best way would be to reinstall foreman with version 1.24.

Actions #17

Updated by Elias Pereira over 4 years ago

Nicolas Odermatt wrote:

I ran into this problem too trying to update Foreman 1.21.3 to 1.22.x. Even though I don't have remote execution installed. In my case its the docker plugin that also relies on foreman-compute. Since I didn't use the docker plugin anymore, I decided to remove it from my system; follow the instructions carefully: https://github.com/theforeman/foreman_docker

Afterwards I followed the Foreman upgrade instructions and was able to run the foreman-installer successfully.

Note: The foreman-compute ist still at the previous version. I don't know why though my guess is that I currently don't use any compute resources. Maybe the best way would be to reinstall foreman with version 1.24.

I uninstalled everything for the remote-execution plugin and upgraded to 1.24.1 and everything ok.

When I tried to install Foreman Remote Execution 1.7 again, error!

Any idea when it will work?

Actions #18

Updated by Anonymous almost 4 years ago

  • Status changed from New to Resolved
Actions

Also available in: Atom PDF