Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1386156

Summary: virt-who with rhev-h and subscription
Product: Red Hat Satellite Reporter: Kenny Tordeurs <ktordeur>
Component: Subscription ManagementAssignee: Eric Helms <ehelms>
Status: CLOSED NOTABUG QA Contact: Katello QA List <katello-qa-list>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.2.2CC: bbuckingham, bkearney, cdonnell, egolov, ehelms, jcallaha, kdixon, lzap, mmccune, rajgupta, rjerrido, xdmoon
Target Milestone: UnspecifiedKeywords: PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-10 16:43:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kenny Tordeurs 2016-10-18 09:58:08 UTC
Description of problem:
Issue: The "Red Hat Enterprise Linux Server, Standard (1-2 sockets) (Unlimited guests) with Smart Management" cannot be assigned to both the rhev-h and the virt-who-rhev-h at the same time but this subscription, Our documentation currently states this is how virt-who should be configured as per [1]

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

How reproducible:
100%

Steps to Reproduce:
1. Configure virt-who to add rhev-h to your satellite
2. Have a "Red Hat Enterprise Linux Server, Standard (1-2 sockets) (Unlimited guests) with Smart Management" subscription in manifest
3. Cannot assign the above subscription to both the RHEV-H and the virt-who-rhev-h content host

Actual results:
- Your RHEV-H is not subscribed properly if above subscription is not assigned there
- Your VMs do not have their DERIVED SKU if above subscription is not assigned there

Expected results:
Have a different subscription or only 1 profile for the RHEV-H

Additional info:
We were able to get things working for your clients in the following setup:
- Assign a "Red Hat Enterprise Linux Server, Standard (1-2 sockets) (Unlimited guests) with Smart Management" to the virt-who-rhevx-1 content host
- To the actual RHEV-H content host we assign the following "Red Hat Enterprise Linux Server" + "Red Hat Enterprise Virtualization for Servers, Standard (1 Socket)"
- After that the clients from that rhev-h start seeing their DERIVED SKU and it works fine

Issue: The "Red Hat Enterprise Linux Server, Standard (1-2 sockets) (Unlimited guests) with Smart Management" cannot be assigned to both the rhev-h and the virt-who-rhev-h at the same time but this subscription used to provide you this as before latest Satellite version you did not have those extra virt-who profiles created. But our documentation currently states this is how virt-who should be configured as per [1]

More details about your subscription:
"Red Hat Enterprise Linux Server, Standard (1-2 sockets) (Unlimited guests) with Smart Management"
~~~
10950773	20127628			--SVCRH01VU		Red Hat Enterprise Linux Server (Unlimited Guests)	22-APR-2016	ACTIVE	19-JAN-2016	18-JAN-2019
10950773	20127628			--SVCRH01		Red Hat Enterprise Linux Server	22-APR-2016	ACTIVE	19-JAN-2016	18-JAN-2019
10950773	20127628			--SVCMPVU		Smart Management (Unlimited guests)	22-APR-2016	ACTIVE	19-JAN-2016	18-JAN-2019
~~~

We can see this subscription provides 3 things:
1) Red Hat Enterprise Linux Server (Unlimited Guests) => 500VMs per hypervisor
2) Red Hat Enterprise Linux Server => Subscribe 1 physical host
3) Smart Management (Unlimited guests) => Smart management for 500VMs [3]

Comment 6 Kenny Tordeurs 2017-04-06 07:55:06 UTC
There is also another bug opened related to this: https://bugzilla.redhat.com/show_bug.cgi?id=1415501

Comment 10 Lukas Zapletal 2017-05-03 07:16:32 UTC
Thanks, I would like someone to take a look and evaluate how to approach this by either "splitting" subscription or "merging" the two profiles into one or else.