Bug 1313596

Summary:	remote execution plugin not installed by default on a capsule or satellite
Product:	Red Hat Satellite	Reporter:	Justin Sherrill <jsherril>
Component:	Installation	Assignee:	Stephen Benjamin <stbenjam>
Status:	CLOSED ERRATA	QA Contact:	jcallaha
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	bbuckingham, ehelms, jcallaha, omaciel, stbenjam, will_darton
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 09:03:27 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:

Description Justin Sherrill 2016-03-02 01:27:00 UTC

Description of problem:

When installing a capsule (or satellite) the remote execution ssh plugin is not installed alongside the smart proxy and thus the proxy cannot be used for remote execution

Version-Release number of selected component (if applicable):
6.2 Snap 1

How reproducible:


Steps to Reproduce:
1.  Install a satellite (and a capsule to the existing satellite)
2.  Visit the Capsules page (switching to any context)
3.  look for the remote execution ssh 'feature'.  It should be there with the default installs.

Comment 6 Peter Ondrejka 2016-03-31 10:33:20 UTC

Should the CLI module for remote execution (tfm-rubygem-hammer_cli_foreman_remote_execution) be also installed by default?

Comment 8 Stephen Benjamin 2016-03-31 21:23:24 UTC

I would say not as part of this bug.

Please file an additional bug because we're not installing other CLI plugins too.
For example, hammer_cli_foreman_discovery is also missing.

Comment 9 jcallaha 2016-04-01 14:50:12 UTC

Verified in Satellite 6.2 Beta Snap 6. Remote execution plugins installed by default. Will file a new bug for missing CLI plugins.

Comment 12 errata-xmlrpc 2016-07-27 09:03:27 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:1500