Bug 1388879

Description of problem:

When registering a client with an activation key, the client is not getting assigned subscriptions to all of the Red Hat products that are associated with the key.

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

tfm-rubygem-katello-3.0.0.80-2.1374038_1380486_1384199.el7sat.noarch

Observed on 6.2.2 and 6.2.3

How reproducible:

This happens consistently with the scenario below.

Steps to Reproduce:

1. Enable/Sync the following repositories:
   - Red Hat Satellite Capsule 6.2 for RHEL 7 Server RPMs x86_64
   - Red Hat Enterprise Linux 7 Server RPMs x86_64 7Server

2. Create a content view (e.g. myview) containing the repos from 1. 
3. Publish the content view to library
4. Promote the content view to dev

5. Create an activation key, associating it with dev/myview.
6. Assign the activation key the following subscriptions:
   - Employee SKU (or RHEL)
   - Red Hat Satellite Employee Subscription
7. Update the product content on the activation key so that repos from 1 are enabled during registration.

8. Register a client using the activation key.  E.g.
   subscription-manager register --org="myorg" --activationkey="mykey"

9. From the client,
   yum clean all
   yum repolist

Actual results:

Observe that 'yum repolist' does not include the capsule repo.

From the ui, go to the content host and observe that it does not have the 'Red Hat Satellite Employee Subscription'

Expected results:

The host should have had the subscription, since it was associated with the activation key and it should have been the capsule repository should have been seen in the repolist output.

Additional info:

WORKAROUND:

In the UI
- go to Hosts -> Content Host -> [myHost]
- click Subscriptions
- click Add
- select checkbox next to Red Hat Satellite Employee Subscription
- click Add Selected

From the client:
- subscription-manager refresh
- yum repolist