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.

Bug 993073

Summary:	[6.3.z] [RFE] Client tools should pass up CPU Socket information
Product:	Red Hat Enterprise Linux 6	Reporter:	Chris Pelland <cpelland>
Component:	rhn-client-tools	Assignee:	Stephen Herr <sherr>
Status:	CLOSED ERRATA	QA Contact:	Lukas Pramuk <lpramuk>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.5	CC:	cpelland, cperry, cww, hlemaitr, jentrena, jhutar, lpramuk, mkorbel, mmello, mminar, msuchy, pep, pgervase, pm-eus, rsawhill, sherr, tao, taw, tcameron, xdmoon
Target Milestone:	rc	Keywords:	FutureFeature, Triaged, ZStream
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	rhn-client-tools-1.0.0.1-8.el6	Doc Type:	Enhancement
Doc Text:	* While Satellite 5.3.0 now has the ability to get the number of CPUs via an API call, there was no function to obtain the number of sockets from the registered systems. This update adds a function to get the number of physical CPU sockets in a managed system from Satellite via an API call.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-01 00:47:15 UTC	Type:	---
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:	949640
Bug Blocks:	835616, 924204, 948337, 949615, 949617, 949619, 949620, 949622, 949623

Description Chris Pelland 2013-08-05 15:00:36 UTC

This bug has been copied from bug #949640 and has been proposed
to be backported to 6.3 z-stream (EUS).

Comment 4 Stephen Herr 2013-08-07 13:46:33 UTC

*** Bug 949638 has been marked as a duplicate of this bug. ***

Comment 7 Lukas Pramuk 2013-09-06 17:38:36 UTC

VERIFIED.
rhn-client-tools-1.0.0.1-8.el6.noarch
rhn-setup-1.0.0.1-8.el6.noarch
rhnlib-2.5.22-15.el6.noarch
subscription-manager-1.1.23.1-1.el6_4.x86_64 (installed/uninstalled)

against Satellite-5.6.0-RHEL5-re20130812.0

Reproducer (unregistered client):
1. register client to satellite
2. @webui: navigate to <system> - tab Details - subtab Hardware - section General

Reproducer (registered client):
1. @client: # rhn-profile-sync
2. @webui: navigate to <system> - tab Details - subtab Hardware - section General

REPRO:
Sockets: <empty>

vs.

FIX:
Sockets: 2


>>> old client has sockets field empty, new client reports number of sockets correctly even if subscription-manager was uninstalled
>>> webui corresponds with api results

Comment 9 errata-xmlrpc 2013-10-01 00:47:15 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1384.html