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:
After register the content host using AK, only one repo still enabled *rhel-6-server-rpms* instead of server, supplementary, common, tools, extras and optional. 

Version-Release number of selected component (if applicable):
6.2.7

How reproducible:
100%

Steps to Reproduce:
1. Enable all above repos (RHEL6.5)
2. Create one CV
3. Crete one CCV and add the CV from item 2 *Just publish without promote to one specific lfc*
4. Create one Activation Key and point to the correct release version, library and ccv
5. On AK enable all product content *server, supplementary, common, tools, extras and optional*
6. Register the machine via AK

Actual results:
Only one repo appear enabled *server*

Expected results:
All repos above enabled

Additional info:

Created redmine issue http://projects.theforeman.org/issues/18825 from this bug

So the main reason about this behavior is the subscription-manager version, if your content host have installed one version less then 1.10.7, please update this package and everything will work as expected.

On our lab, after installed the package version 1.18.10 *subscription-manager.x86_64 0:1.18.10-1.el6* everything worked as well.

Thanks all!

Closing this one. Thanks for the resolution.