Hide Forgot
+++ This bug was initially created as a clone of Bug #580924 +++ Description of problem: spacewalk-report always reports 1 CPU even if Details > Hardware show more CPUs. Version-Release number of selected component (if applicable): spacewalk-reports-0.8.2-1 How reproducible: Deterministic. Steps to Reproduce: 1. Have client system with more than one CPU. 2. Register it to Spacewalk server. 3. Look at the /network/systems/details/hardware.pxt?sid=... page, confirm that the number of CPUs is correct in parenthesis. 4. Run spacewalk-reports inventory, check the last field for the system in question. Actual results: 1 CPUs; ... Expected results: Correct number of CPUs. Additional info: --- Additional comment from jpazdziora@redhat.com on 2010-04-09 09:51:56 EDT --- Taking. Fixed in Spacewalk master fe46f64d07c6bcb4fa8607abb49920ce263b20e9. --- Additional comment from jpazdziora@redhat.com on 2010-05-03 07:39:20 EDT --- Tagged in master as spacewalk-reports-0.9.1-1. Tagged again as spacewalk-reports-1.0.1-1 for Spacewalk 1.0. Moving ON_DEV. --- Additional comment from jpazdziora@redhat.com on 2010-05-03 07:43:02 EDT --- Moving ON_QA as the package is in Spacewalk 1.0 repo, for example http://spacewalk.redhat.com/yum/1.0/RHEL/5/i386/spacewalk-reports-1.0.1-1.el5.noarch.rpm for 32bit RHEL 5.
Bugzilla for errata for Satellite 5.3.x.
Taking.
Cherry-picked to Satellite repo, 12c0b304a7c42ed479d2fc34a4d3e8eec1cdbb4d. Tagged as spacewalk-reports-0.7.0-4-sat.
# VERIFIED the spacewalk-reports 0.7.0-4 was checked against RHEL4 and RHEL5 installed Satellites - for the systems with >1 CPUs the correct information is reporting. RHTS tests launched for checking regression issues found no problem as well. thanks a lot for the fix.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0397.html