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:
On physical hosts running as hypervisor (libvirt, openstack compute, etc) that have a RHCI entitlement guests will be entitled to the unlimited virtual subscription partof the same RHCI subscription. The mapping si done using virt-who or katello_notification. However, when the guests on these hypervisors are in different orgnaizations. This does not work

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


How reproducible:


Steps to Reproduce:
1. Build hypervisor with virt-who and RHCI subscription from Sat6 - org1
2. Provision guests from sat6 - org1 on this hypervisor
3. Try to provision guests from sat6 - org2 on this hypervisor

Actual results:


Expected results:


Additional info:

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

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