Bug 1036433

Summary:	Subscripting to JBoss Enterprise Web Server entitlement on 4 core Virtual Machines consumes 16 cores
Product:	Red Hat Enterprise Linux 6	Reporter:	Jason Shepherd <jshepherd>
Component:	subscription-manager	Assignee:	candlepin-bugs
Status:	CLOSED WORKSFORME	QA Contact:	John Sefler <jsefler>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.6	CC:	brad.webb, ckozak, dgoodwin, jshepherd
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-21 13:34:51 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:
Bug Depends On:
Bug Blocks:	863175

Description Jason Shepherd 2013-12-02 00:09:02 UTC

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:

Comment 2 RHEL Program Management 2013-12-06 09:25:42 UTC

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.

Comment 3 Devan Goodwin 2014-01-17 15:25:50 UTC

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.

Comment 4 brad.webb 2014-01-21 06:01:24 UTC

I cannot replicate issue. Please close.