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.
Description of problem:
Unlimited derived skus were not given out for sku MCT2862S when the parent subscription was attached to a hypervisor. The hypervisor is hosted on vmware and given 2 sockets. The unlimited child skus only showed up to be applied when a VDC subscription and this sku were applied to the hypervisor. When the VDC subscription was removed the OSE subscription still functioned as it should.
How reproducible:
So far - not able to reproduce.
Steps to Reproduce:
1. Apply SKU to hypervisor
2. Navigate to host under hypervisor to see if an unlimited subscription is available
3. If not available, apply VDC (or potentially any other sub) as well as this SKU and observe changes to available subscriptions on host.
Additional info:
Found in SFDC # 01694803
This may be related to bug 1366327; however, the scenario above would need to be tested with a fully updated Satellite 6.2.2 (once erratum is available) using the customer's manifest.
This bug was unable to be recreated and the customer did not run into this again. The customer has since upgraded satellite packages and has used the same sku without trouble. Closing the bz accordingly.