Bug 1339336

Summary: unable to install remote execution on capsule: "ERROR: Unrecognised option '--foreman-proxy-plugin-remote-execution-ssh-enabled'"
Product: Red Hat Satellite Reporter: Jan Hutař <jhutar>
Component: InstallationAssignee: Martin Bacovsky <mbacovsk>
Status: CLOSED ERRATA QA Contact: Lukas Zapletal <lzap>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, cwelton, ehelms, jhutar, lpramuk, lzap, mhulan, psuriset
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: katello-installer-base-3.0.0.42-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1359816 (view as bug list) Environment:
Last Closed: 2016-07-27 11:19:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1359816    

Description Jan Hutař 2016-05-24 18:20:01 UTC
Description of problem:
There ar unclear install options in "--help" output for remote execution plugin


Version-Release number of selected component (if applicable):
satellite-capsule-6.2.0-12.1.el7sat.noarch


How reproducible:
always


Steps to Reproduce:
1. # satellite-installer --scenario capsule --help


Actual results:
[...]
= Module foreman_proxy_plugin_remote_execution_ssh:
    --enabled                     enables/disables the plugin (default: true)
    --enabled                     enables/disables the pulp plugin (default: false)
    --enabled                     Enables/disables the plugin (default: true)
    --generate-keys               Automatically generate SSH keys (default: true)
    --listen-on                   Proxy feature listens on http, https, or both (default: "https")
    --listen-on                   Proxy feature listens on https, http, or both (default: "https")
    --listen-on                   Proxy feature listens on http, https, or both (default: "https")
    --local-working-dir           Local working directory on the smart proxy (default: "/var/tmp")
    --remote-working-dir          Remote working directory on clients (default: "/var/tmp")
    --ssh-identity-dir            Directory where SSH keys are stored (default: "/usr/share/foreman-proxy/.ssh")
    --ssh-identity-file           Provide an alternative name for the SSH keys (default: "id_rsa_foreman_proxy")
    --ssh-keygen                  Location of the ssh-keygen binary (default: "/usr/bin/ssh-keygen")


Expected results:
Each option should be there only once.

Comment 1 Jan Hutař 2016-05-24 18:29:25 UTC
Hmm, when I use "--scenario satellite" it gives me more expected option names:

= Module foreman_proxy_plugin_remote_execution_ssh:
    --foreman-proxy-plugin-remote-execution-ssh-enabled  Enables/disables the plugin (default: true)
    --foreman-proxy-plugin-remote-execution-ssh-generate-keys  Automatically generate SSH keys (default: true)
    --foreman-proxy-plugin-remote-execution-ssh-listen-on  Proxy feature listens on https, http, or both (default: "https")
    --foreman-proxy-plugin-remote-execution-ssh-local-working-dir  Local working directory on the smart proxy (default: "/var/tmp")
    --foreman-proxy-plugin-remote-execution-ssh-remote-working-dir  Remote working directory on clients (default: "/var/tmp")
    --foreman-proxy-plugin-remote-execution-ssh-ssh-identity-dir  Directory where SSH keys are stored (default: "/usr/share/foreman-proxy/.ssh")
    --foreman-proxy-plugin-remote-execution-ssh-ssh-identity-file  Provide an alternative name for the SSH keys (default: "id_rsa_foreman_proxy")
    --foreman-proxy-plugin-remote-execution-ssh-ssh-keygen  Location of the ssh-keygen binary (default: "/usr/bin/ssh-keygen")

But these options do not work with "--scenario capsule".

Comment 3 Jan Hutař 2016-05-25 09:13:18 UTC
Changing summary to highlight more important issue:

> # satellite-installer --scenario capsule --foreman-proxy-plugin-remote-execution-ssh-enabled
> ERROR: Unrecognised option '--foreman-proxy-plugin-remote-execution-ssh-enabled'
> 
> See: 'foreman-installer --help'

Comment 4 Jan Hutař 2016-05-25 12:40:45 UTC
To make this clearer: I want to perform remote command (via remote execution plugin) on system registered through Capsule. Because of this bug I can not install remote execution plugin to Capsule. On Satellite it installs fine and when I register client directly to satellite, I can schedule remote commad on such a system as expected.

Comment 5 Marek Hulan 2016-06-01 09:57:07 UTC
It seems we need to enable prefixes now when capsule-installer is no-longer single puppet module based. Which means we'll have to provide a migration for capsule 6.1 answer file.

Comment 8 Bryan Kearney 2016-06-01 14:17:17 UTC
Upstream bug assigned to mbacovsk

Comment 9 Bryan Kearney 2016-06-01 14:17:20 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/13908 has been closed

Comment 12 Lukas Zapletal 2016-07-15 15:48:02 UTC
VERIFIED SNAP20

[root@sgi-xe270-01 ~]# rpm -q katello foreman foreman-ovirt tfm-rubygem-rbovirt
katello-3.0.0-10.el7sat.noarch
foreman-1.11.0.48-1.el7sat.noarch
foreman-ovirt-1.11.0.48-1.el7sat.noarch
tfm-rubygem-rbovirt-0.0.37-1.el7sat.noarch

[root@sgi-xe270-01 ~]# satellite-installer --foreman-proxy-plugin-remote-execution-ssh-enabled true -v
...
[ INFO 2016-07-15 11:46:53 verbose] Puppet has finished, bye!
[ INFO 2016-07-15 11:46:53 verbose] Executing hooks in group post
  Success!
  * Satellite is running at https://sgi-xe270-01.rhts.eng.bos.redhat.com
  * To install additional capsule on separate machine continue by running:

      capsule-certs-generate --capsule-fqdn "$CAPSULE" --certs-tar "~/$CAPSULE-certs.tar"

  The full log is at /var/log/foreman-installer/satellite.log
[ INFO 2016-07-15 11:46:53 verbose] All hooks in group post finished

Comment 13 Bryan Kearney 2016-07-27 11:19:14 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