Bug 1142839

Description of problem:
Customers who wish to use unlimited/Virtual Data Center (vDC) subscriptions with Subscription Management Platforms in Satellite 6 are running into challenges preventing them from successfully using these subscriptions in Multi-Org Setups. In multi-org setups, customers can only associate these subscriptions with a single organization, even though these subscriptions are sold as 'infrastructure' products.  This puts our customers in a situation where our management tools are not allowing them to use the product in the manner in which it is sold and understood.

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

How reproducible:
Always

Steps to Reproduce:
1. Add 'Virtual Data Center Subscriptio'n to Org 1
2. Attach a system in Org 2 to the 'Virtual Data Center Subscription' from Org 1

Actual results:
Does not work

Expected results:
Have the ability to share Virtual Data Center Subscription accross multiple organization within Satellite 6

Additional info:
When a customer purchases a unlimited/vDC subscription, it is generally done because they have reached a sufficient density of RHEL systems in their virtual environment to necessitate this product. Effectively, the spirit of this product is 'buy it for the infrastructure and use as needed'. However, when a customer wishes to leverage one of these subscriptions with a product that leverages Candlepin in multi-org configurations, they will be unable to.

Example:
Customer has an environment with 1 Hypervisor which they wish to run 15 virtual guests on. Customer purchases a vDC sub, (RH00001 - Red Hat Enterprise Linux for Virtual Datacenters - Premium). Their expectation, supported by our Enterprise Agreement (and also the spirit of how we sell those products) is that it doesn't matter HOW they use the subscription, as long as those 15 guests reside on that single Hypervisor, they are well within the T's & C's, and we won't unleash SEAP on them

The customer with the singular hypervisor and the 15 guests wishes to create two Satellite 6 organizations (Engineering / Development) to separate responsibilities and split them 8/7 between the two orgs. Next they:

 - Install Satellite 6
 - Create a subscription management application for the Engineering org in the portal, and attach the RH00001 - Red Hat Enterprise Linux for Virtual Datacenters sub to it.
 - Download and import the subscription manifest for the Engineering org

What happens next is that:

 - There is no subscription left for the Development Org. (It has been consumed in the Engineering Org)
 - The customer can leverage neither the vDC subscription (from the Engineering Org) nor can they leverage any host-guest mapping data from the Engineering Org.

 
Even though the 15 guests reside on the single hypervisor, only 8 of them (the ones in the Engineering Org) will have a valid sub. The 7 in the Development Org will not. The customer's (completely accurate) experience at the end of this process is that the tooling isn't allowing them to do what we sold them the product to do, which was 'buy it for the infrastructure and use as needed'. Additionally, they may get the mistaken understanding that since the 7 guests in the Development Org don't have valid subs that they'd need to procure additional subs to cover them. Both situations lead to a very bad customer experience.


This bug is at some point related to https://bugzilla.redhat.com/show_bug.cgi?id=1142315 - but we'd like to track both with seperate bugs

Please also note, some associate might feel that this is not a bug but more likely a RFE. We have had a discussion on this topic and found, as it prevents the customer from using the subscription in the spirit in which it was sold for we raise it as a bug.