Bug 586344

Summary: /usr/sbin/rhn-profile-sync failes when running stuff from python-dmidecode
Product: Red Hat Enterprise Linux 5 Reporter: Morten Werner Forsbring <werner>
Component: python-dmidecodeAssignee: David Sommerseth <davids>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: low Docs Contact:
Priority: low    
Version: 5.5CC: davids, ovasik, t.h.amundsen
Target Milestone: rc   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-21 09:44:01 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
Content from /usr/share/rhn/up2date_client/hardware.py to reproduce the error none

Description Morten Werner Forsbring 2010-04-27 07:20:39 EDT
Created attachment 409441 [details]
Content from /usr/share/rhn/up2date_client/hardware.py to reproduce the error

Description of problem:
When /usr/sbin/rhn-profile-sync runs, we get this error from python-dmidecode:
python: src/dmidecode.c:4083: dmi_decode: Assertion `sub_n != ((void *)0)' failed.
Aborted

Version-Release number of selected component (if applicable):
dmidecode-2.10-3.el5
python-dmidecode-3.10.8-4.el5

How reproducible:
Every time on two different hardware models (three boxes):

 * HP Compaq dc7100 SFF(DX878AV)
 * HP Compaq dc7100 SFF(PE218ET)

Steps to Reproduce:
I'll add a small python-script which can be used to reproduce the error on
the three boxes we experience problems.
  
Actual results:
nemi /# /tmp/pydmitest 
python: src/dmidecode.c:4083: dmi_decode: Assertion `sub_n != ((void *)0)' failed.
Aborted
nemi /#

Expected results:
mariner /# /tmp/pydmitest 
mariner /#
Comment 1 David Sommerseth 2010-05-21 09:44:01 EDT
Thank you for reporting this issue.  This particular issue seems to have been reported in bug #583867.  Thus marking this bug as a duplicate, as I believe the solution will be closed with that fix.

*** This bug has been marked as a duplicate of bug 583867 ***