Bug 1322360

Created from redmine issue http://projects.theforeman.org/issues/11369

*** Bug 1331258 has been marked as a duplicate of this bug. ***

Upstream bug assigned to aruzicka

Upstream bug assigned to aruzicka

FailedQA.

@satellite-capsule-6.2.0-20.3.el6sat.noarch          
rubygem-smart_proxy_dynflow-0.1.3-1.el6sat.noarch
rubygem-smart_proxy_remote_execution_ssh-0.1.2-2.el6sat.noarch

# satellite-installer --enable-foreman-proxy-plugin-remote-execution-ssh
 Could not start Service[smart_proxy_dynflow_core]: Execution of '/sbin/service smart_proxy_dynflow_core start' returned 1: Starting smart_proxy_dynflow_core: /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/dependency.rb:315:in `to_specs': Could not find 'rake' (>= 0) among 28 total gem(s) (Gem::LoadError)
 /Stage[main]/Foreman_proxy::Plugin::Dynflow/Service[smart_proxy_dynflow_core]/ensure: change from stopped to running failed: Could not start Service[smart_proxy_dynflow_core]: Execution of '/sbin/service smart_proxy_dynflow_core start' returned 1: Starting smart_proxy_dynflow_core: /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/dependency.rb:315:in `to_specs': Could not find 'rake' (>= 0) among 28 total gem(s) (Gem::LoadError)
Installing             Done                                               [100%] [....................................]
  Something went wrong! Check the log for ERROR-level output
  The full log is at /var/log/foreman-installer/capsule.log


# service smart_proxy_dynflow_core start
Starting smart_proxy_dynflow_core: /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/dependency.rb:315:in `to_specs': Could not find 'rake' (>= 0) among 28 total gem(s) (Gem::LoadError)
Checked in 'GEM_PATH=/opt/theforeman/tfm/root/usr/share/gems:/opt/rh/rh-ror41/root/usr/share/gems:/usr/share/foreman-proxy/.gem/ruby:/opt/rh/rh-ruby22/root/usr/share/gems:/opt/rh/rh-ruby22/root/usr/local/share/gems/opt/rh/rh-ror41/root/usr/share/gems:/opt/rh/rh-ruby22/root/usr/local/share/gems', execute `gem env` for more information
	from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/specification.rb:1311:in `block in activate_dependencies'
	from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/specification.rb:1300:in `each'
	from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/specification.rb:1300:in `activate_dependencies'
	from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/specification.rb:1282:in `activate'
	from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/specification.rb:1314:in `block in activate_dependencies'
	from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/specification.rb:1300:in `each'
	from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/specification.rb:1300:in `activate_dependencies'
	from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/specification.rb:1282:in `activate'
	from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/specification.rb:1314:in `block in activate_dependencies'
	from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/specification.rb:1300:in `each'
	from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/specification.rb:1300:in `activate_dependencies'
	from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/specification.rb:1282:in `activate'
	from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_gem.rb:67:in `block in gem'
	from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_gem.rb:66:in `synchronize'
	from /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_gem.rb:66:in `gem'
	from /usr/bin/smart_proxy_dynflow_core:22:in `<main>'

This seems like a packaging issue on capsule, where there are some missed rake dependency in the spec and it happens only on capsule, not the main server, both on rhel6 and rhel7

The workaround should be to run:

  yum install -y rh-ruby22-rubygem-rake
  satellite-installer

This works both at the first run and also if one needs to fix the issue later.

The problem was with the apipie-params gem having `rake` in the dependencies. This was fixed in upstream https://github.com/iNecas/apipie-params/pull/2 and released in apipie-params-0.0.5

Dev Verified this on SNAP 21.1:

[root@dhcp-8-29-12 ~]# satellite-installer --enable-foreman-proxy-plugin-remote-execution-ssh
Installing             Done                                               [100%] [..........................................................................................................................................................]
  Success!
  The full log is at /var/log/foreman-installer/capsule.log
[root@dhcp-8-29-12 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.8 (Santiago)
[root@dhcp-8-29-12 ~]#

VERIFIED.

@satellite-capsule-6.2.0-21.1.el6sat.noarch
foreman-installer-1.11.0.9-1.el6sat.noarch
tfm-rubygem-apipie-params-0.0.5-2.el6sat.noarch

Verified @standalone capsule on RHEL6

1)
# satellite-installer --enable-foreman-proxy-plugin-remote-execution-ssh
Installing             Done                                               [100%] [....................................]
  Success!
  The full log is at /var/log/foreman-installer/capsule.log

2)
@satellite # hammer capsule info --id 2
Id:         2
Name:       <CAPSULE_FQDN>
URL:        https://<CAPSULE_FQDN>:9090
Features:   
    Templates
    Puppet
    Puppet CA
    Discovery
    Pulp Node
    Dynflow
    SSH
Created at: 2016/07/22 09:57:40
Updated at: 2016/07/22 10:54:20

>>> standalone capsule SSH feature was enabled

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1501