Hide Forgot
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.