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:
Currently we can either set a subnet (and remote execution capsule through the subnet) or distribute all capsule ssh keys to all clients in case a subnet isn't defined for a host. In some environments with a lot of subnets this ends up being inconvenient. 

If the content source is set for a host (via host group) it would seem that the preferred capsule has already been chosen for the host. In these cases, it would be more convenient to distribute only the content source ssh key and define the remote execution capsule for the particular host as well.

This should already be the case currently: we look at the all capsules assigned to the host with remote execution feature and use it as pool of capsules to be used.

If that is not the case, see https://bugzilla.redhat.com/show_bug.cgi?id=1508153#c3 for providing more info on the current setup.

The issue here for this customer was that there is a large pool of capsules (12) and an even larger pool of subnets, where making a host group for each subnet would mean managing more than 40 or 50 subnets/hostgroups. In this case, the only reason for making so many would be to provide a 'specific' capsule for remote execution.

If we're already defining a content_source to be a specific capsule, we could define that same capsule as the remote execution capsule as well and offer another way to be specific for the remote execution capsule (and eliminate the need to distribute 12 ssh keys to all content hosts or manage a host group for each subnet).

*** This bug has been marked as a duplicate of bug 1244112 ***