Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1322360 - Support for smart proxy on RHEL6
Summary: Support for smart proxy on RHEL6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Adam Ruzicka
QA Contact: Lukas Pramuk
URL: http://projects.theforeman.org/issues...
Whiteboard:
: 1331258 (view as bug list)
Depends On:
Blocks: 1347201
TreeView+ depends on / blocked
 
Reported: 2016-03-30 11:50 UTC by Ivan Necas
Modified: 2019-09-26 14:47 UTC (History)
7 users (show)

Fixed In Version: foreman-installer-1.11.0.9-1,rubygem-apipie-params-0.0.5-2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:11:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 11369 0 None None None 2016-04-22 16:25:14 UTC

Description Ivan Necas 2016-03-30 11:50:01 UTC 
The smart_proxy_dynflow requires at least Ruby 1.9.3 to work properly. We need to find a way how to run it on the RHEL6.
Comment 1 Ivan Necas 2016-03-30 11:50:03 UTC 
Created from redmine issue http://projects.theforeman.org/issues/11369
Comment 3 Stephen Benjamin 2016-04-28 12:40:48 UTC 
*** Bug 1331258 has been marked as a duplicate of this bug. ***
Comment 5 Bryan Kearney 2016-05-20 08:13:43 UTC 
Upstream bug assigned to aruzicka
Comment 6 Bryan Kearney 2016-05-20 08:13:45 UTC 
Upstream bug assigned to aruzicka
Comment 12 Lukas Pramuk 2016-07-21 05:11:44 UTC 
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>'
Comment 14 Ivan Necas 2016-07-21 07:18:56 UTC 
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.
Comment 16 Ivan Necas 2016-07-21 08:11:49 UTC 
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
Comment 19 Mike McCune 2016-07-22 05:59:38 UTC 
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 ~]#
Comment 20 Lukas Pramuk 2016-07-22 11:13:29 UTC 
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
Comment 21 Bryan Kearney 2016-07-27 11:11:00 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.