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:
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.
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.
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.