Bug 949640
Summary: | [RFE] Client tools should pass up CPU Socket information | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Stephen Herr <sherr> |
Component: | rhn-client-tools | Assignee: | Stephen Herr <sherr> |
Status: | CLOSED ERRATA | QA Contact: | Martin Korbel <mkorbel> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.5 | CC: | abienven, cpelland, cperry, cww, hlemaitr, jentrena, jhutar, mkorbel, mmello, mminar, msuchy, pep, pgervase, rsawhill, 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: | 948326 | Environment: | |
Last Closed: | 2013-07-17 09:24:10 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 | ||
Bug Blocks: | 924204, 948337, 949615, 949617, 949619, 949620, 949622, 949623, 960054, 993073, 993076 |
Description
Stephen Herr
2013-04-08 17:04:54 UTC
*** Bug 949639 has been marked as a duplicate of this bug. *** VERIFIED on Satellite-5.6.0-RHEL6-re20130607.1 Satellite: - spacewalk-java-1.9.83-42.el6sat - spacewalk-schema-1.9.38-17.el6sat - spacewalk-backend-1.9.46-18.el6sat Client RHEL 6.4 x86_64: - rhn-setup-1.0.0.1-4.el6 or older (empty field) - rhn-setup-1.0.0.1-8.el6 or newer (it shows correct number of socket) 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-1087.html |