Bug 948337

Summary: [RFE] Client tools should pass up CPU Socket information
Product: [Community] Spacewalk Reporter: Stephen Herr <sherr>
Component: ClientsAssignee: Stephen Herr <sherr>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: high Docs Contact:
Priority: high    
Version: 1.9CC: cperry, cww, jentrena, mmello, mminar, msuchy, pep, pgervase, rsawhill, tao, taw, tcameron, tkasparek, xdmoon
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: rhn-client-tools-1.10.7-1 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 948326 Environment:
Last Closed: 2013-08-02 13:11:30 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: 596917, 948326, 948335, 949615, 949617, 949619, 949620, 949622, 949623, 949637, 949638, 949639, 949640, 990664, 993073    
Bug Blocks: 991452    

Description Stephen Herr 2013-04-04 15:35:43 UTC 
+++ This bug was initially created as a clone of Bug #948335 +++

Bug 948335 describes the desire to have CPU Socket information available from Satellite. This requires two different logical steps.

1) The RHEL client tools must be updated to pass socket information to Satellite
2) Satellite must be updated to store / display socket information

This bug will track the development and release of #1, the client tools portion. Bug 948335 will track the development and release of #2, the Satellite portion. Both will be necessary for this functionality to work.
Comment 1 Stephen Herr 2013-04-04 15:40:44 UTC 
Spacewalk master: 36c64513d68cad3a3973d76de91529f473afdd15
Comment 2 Stephen Herr 2013-05-28 21:16:18 UTC 
Also:
e0210e92c2b41c071f7b6361b80ba0ae7cda87f0

Make the client only send up socket information if the server has the capability to receive.
Comment 3 Tomáš Kašpárek 2013-08-02 13:11:30 UTC 
Fix for this bug is present in Spacewalk 2.0, closing this bug as CURRENTRELEASE.