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:
Bare metal hosts consume twice the quantity of subscriptions appropriate to the actual socket count.


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

How reproducible:
always, in my demo environment and at customer site

Steps to Reproduce:
1. Register new one or two socket bare metal host to Sat 6.2.10
2. run auto attach (or assign subscription manually)
3. look at Content Hosts -> Subscriptions Quantity or run "subscription-manager list --consumed" on that host

Actual results:
Quantity Used: 2

Expected results:
Quantity Used: 1

Additional info:
With our engineering manifest auto-attach uses ONE Hyperscale, Standard (5 Physical Nodes) subscription or you need to attach TWO regular RHEL subs

This is explained in https://access.redhat.com/blogs/1169563/posts/2882741

Not a bug.