Bug 1327665

Summary:	Enable remote execution plugin by default during capsule installation
Product:	Red Hat Satellite	Reporter:	jcallaha
Component:	Installer	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED NOTABUG	QA Contact:	Katello QA List <katello-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	bbuckingham, ehelms, jcallaha, mhulan, mmccune, ohadlevy, riehecky, stbenjam, xdmoon
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:	2017-07-13 13:09:01 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:

Description jcallaha 2016-04-15 15:18:33 UTC

Description of problem:
We do not current enable remote execution on capsule installs. With this being a default feature for Satellite, we should enable it by default for capsules, too.

Version-Release number of selected component (if applicable):
Satellite 6.2 Beta Snap 8 Compose 1.

How reproducible:
Install a capsule

Steps to Reproduce:
1. Setup a Capsule without specifying the remote execution plugin should be enabled.
2. Check to see if the remote execution feature was enabled

Actual results:
Remote Execution was not enabled.

Expected results:
Remote execution was installed.

Comment 2 jcallaha 2016-04-22 18:08:32 UTC

the installer flag should be
--enable-foreman-proxy-plugin-remote-execution-ssh

Comment 4 Mike McCune 2016-05-16 06:08:52 UTC

Capsules are intended to be more flexible in their deployment model and I don't think we should necessarily require by default that REX be enabled on the capsule.

I'm going to remove the blocker flag and keep this under consideration for 6.2.z as we get feedback from customers.

Comment 11 jcallaha 2017-07-13 13:09:01 UTC

It could be best to allow capsules to be as minimal/flexible as possible. In this sense, if a customer doesn't want to have RE enabled on their capsules, they shouldn't have to explicitly define that during installation. 

I am going to close this as not a bug. If a customer requests that this be implemented, they are welcome to open a case and we can revisit the proposal at that time.