1. What is the nature and description of the request?
-->
When configuring virt-who for RHEV or RHEL-OSP hypervisors/compute nodes, the proper configuration of virt-who is complex and complicated by the fact that the user may also register the hypervisor/compute nodes via subscription-manager. This effectively creates multiple consumer records within Candlepin making it difficult to properly attach subscriptions.

2. Why does the customer need this? (List the business requirements here)
-->
Most subscriptions that are sold for RHV/RHEL-OSP include content for
both the hypervisor AND its guests. And since we cannot 'break' a
subscriptions components across two host records, the customer ends up
in a situation where they do not have enough subscriptions to properly
subscribe both hypervisors.

3. How would the customer like to achieve this? (List the functional requirements here)
--> There should be only one profile created for RHEV/RHEL OSP hypervisors through which Hypervisor can get updates and guests running on the hypervisor can inherit subscription.