Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
I'm unable to install remote execution plugin to external capsule and it is not just a matter of unclear options you can pass to installer. There is also some package dependency issues.
Version-Release number of selected component (if applicable):
satellite-capsule-6.2.4-1.0.el7sat.noarch
Installing from repo synced from CDN just few minutes ago
How reproducible:
always
Steps to Reproduce:
1. Install Satellite 6.2.4 from CDN, sync RHEL and Capsule repos (all at RHEL7)
2. Install capsule with command generated with `capsule-certs-generate`
3. Rerun the command with "--foreman-proxy-plugin-remote-execution-ssh-enabled true --foreman-proxy-plugin-remote-execution-ssh-generate-keys true"
4. Rerun the command with "--enable-foreman-proxy-plugin-remote-execution-ssh" or "--foreman-proxy-plugin-remote-execution-ssh-enabled true"
Actual results:
In step 3, it has no effect. It is very confusing why not.
In step 4, both varians have same effect. Again, it is confusing to have 2 (or 3) different options for one functionality (i.e. installing the plugin).
But core of the problem is that commands from 4 ends with "Something went wrong!". Also manual yum install fails with dependency issues
Expected results:
Remote execution plugin should be installable
Indeed, the options are confusing.
This:
--foreman-proxy-plugin-remote-execution-ssh-enabled true
sets the "enabled" option in /etc/foreman-proxy/settings.d/remote_execution_ssh.yml file. That's already the default, this setting is used when you want the plugin to be installed, but just to temporarily disable it.
The only option you want is only "--enable-foreman-proxy-plugin-remote-execution-ssh", which actually installs and configures the package.
In 6.3, we make this more clear by only making the relevant option visible to the user. That was part of BZ1124553, although we're still looking at a better solution.
Once you used the right installer setting, the source of the problem is in the capsule.log:
[ERROR 2016-12-07 01:26:55 main] Execution of '/usr/bin/yum -d 0 -e 0 -y install tfm-rubygem-smart_proxy_remote_execution_ssh_core' returned 1: Error: Package: tfm-rubygem-apipie-params-0.0.5-2.el7sat.noarch (rhel-7-server-satellite-capsule-6.2-rpms)
[ INFO 2016-12-07 01:26:55 main] Requires: rh-ruby22-ruby(rubygems)
For REX, the capsule needs SCL, see Section 4.3:
https://access.redhat.com/documentation/en/red-hat-satellite/6.2/paged/installation-guide/chapter-4-installing-capsule-server