Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1327665 - Enable remote execution plugin by default during capsule installation
Enable remote execution plugin by default during capsule installation
Status: CLOSED NOTABUG
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Installer (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity high (vote)
: Unspecified
: Unused
Assigned To: satellite6-bugs
Katello QA List
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-04-15 11:18 EDT by jcallaha
Modified: 2017-07-13 09:09 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-07-13 09:09:01 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description jcallaha 2016-04-15 11:18:33 EDT
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 14:08:32 EDT
the installer flag should be
--enable-foreman-proxy-plugin-remote-execution-ssh
Comment 4 Mike McCune 2016-05-16 02:08:52 EDT
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 09:09:01 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.