Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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:

Register a RHEL 6 system with Subscription Manager and subscribe to 'jb-ews-2-i386-server-6-rpm', or 'jb-ews-2-x86_64-server-6-rpm' on a Virtual Machine with 4 CPU sockets. Notice that all of a 16 core subscription is consumed, and you can't register to those channels on another Virtual Machine running RHEL with less than your remaining number of CPU Sockets.


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


How reproducible:


Steps to Reproduce:
1. Register a RHEL 6 system with 4 CPU sockets to Subscription Manager and subscribe to 'jb-ews-2-i386-server-6-rpm', or 'jb-ews-2-x86_64-server-6-rpm'
2. Try and Register another RHEL 6 Virtual Machine with less than 12 CPU Sockets.

Actual results:

The 2nd System can't register


Expected results:

The 1st System consumes 4 CPU sockets of a 16 core entitlement, and the 2nd machine can register with remaining cores from entitlement.


Additional info:

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Is this issue still occurring? We'll need some additional information if possible.

Can we get output of subscription-manager list --consumed on the system which is getting subscribed?

Also subscription-manager facts --list (from *both* systems).

Might need some more but this would be a good start for us. Thanks.

I cannot replicate issue. Please close.