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:

Capsule installed with --pulp="false" so not working as content provider, is working as relay for content requests to satellite. 




Steps to Reproduce:
1. Install satellite
2. Install Isolated capsule without pulp and registered to capsule
3. Register the client on another isolated network which does not have access to satellite to capsule. 

Actual results:

Cant even register to capsule

Expected results:

Register to capsule and capsule is working only as relay to content requests to satellite

client can work as registered directly to the satellite. 

Additional info:

main advantage of this is saving storage space when capsule is not required to work also as content provider.

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