Bug 580924 - spacewalk-report always reports 1 CPU
Summary: spacewalk-report always reports 1 CPU
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 0.8
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jan Pazdziora
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space09 588277 593584
TreeView+ depends on / blocked
 
Reported: 2010-04-09 13:50 UTC by Jan Pazdziora
Modified: 2010-05-19 08:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 588277 593584 (view as bug list)
Environment:
Last Closed: 2010-05-05 14:57:13 UTC
Embargoed:

Attachments (Terms of Use)

Description Jan Pazdziora 2010-04-09 13:50:18 UTC 
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:
Comment 1 Jan Pazdziora 2010-04-09 13:51:56 UTC 
Taking.

Fixed in Spacewalk master fe46f64d07c6bcb4fa8607abb49920ce263b20e9.
Comment 2 Jan Pazdziora 2010-05-03 11:39:20 UTC 
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.
Comment 3 Jan Pazdziora 2010-05-03 11:43:02 UTC 
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.
Comment 6 Miroslav Suchý 2010-05-05 14:57:13 UTC 
This bug has been fixed in Spacewalk 1.0.
Closing.
Note You need to log in before you can comment on or make changes to this bug.