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:
Custom repos are not available  under system --> All --> select registered system --> subscription tab

I created a custom product via content--> Product and later promote it to next env(test). Then registered a system with env test.

Version-Release number of selected component (if applicable):
katello-1.4.8-1.git.37.b37a904.el6.noarch


How reproducible:
always

Steps to Reproduce:
1. Created custom product/repo
2. Publish it and promote it to next env 'test'
3. register a system vai rhsm against env 'test'
4. Go to system-. All --> select registered system --> susbscriptions tab

Actual results:
custom repos are not available to subscribe

Expected results:
user should be able to subscribe a system to custom repos from system's subscription tab

Additional info:

In this case did the system get registered to 'test' or to 'test/VIEW_NAME', 

The statement:  register a system vai rhsm against env 'test'  indicates it was against just the environment, which really shouldn't have been possible.

I registered the system against just the env 'test'.

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