Bug 630095

Summary: rhnreg_ks fails with Assertion error from file 'dmidecode.c'
Product: Red Hat Satellite 5 Reporter: Pavel Novotny <pnovotny>
Component: RegistrationAssignee: Michael Mráka <mmraka>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satellite-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 540CC: cperry
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-07 08:57:30 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 487677    

Comment 1 Clifford Perry 2010-09-06 10:30:14 EDT
This is a CLIENT bug, please report it as such. 

I am 100% if you tried the same test to a RHN Hosted or Sat 5.3 code base, the same error would occur. 

Using a no hardware or skip hardware option should by-pass this bug to allow registration to complete.

Comment 2 Michael Mráka 2010-09-06 10:47:21 EDT

To all developers reading this I have discovered the route of the problem but could probably do with some sort of workaround for others;

Basically as you know, when the system attaches itself to the server it collects a load of  hardware information, this calls upon dmidecode which scans /dev/mem.

The error although seemingly random seemed to happen on boxes that had a loud of dodgy information in /dev/mem. I could get the servers connecting to spacewalk by deleting the /dev/mem device (or renaming it for the rhnreg_ks command and then rename it back).

I think there should be a workaround for this since this information was nowhere on the internet. Should I raise a bug report since this was happening to me 1 in 4 servers.

Comment 4 Michael Mráka 2010-09-07 04:45:00 EDT
Please report version of dmidecode and python-dmidecode.
Comment 5 Pavel Novotny 2010-09-07 08:57:30 EDT
Package versions:


I found out this bug has been already fixed in bug 596133 in python-dmidecode-3.10.13-1.el5_5.1 and related errata RHBA-2010:9824-04 has been verified.
Now it is waiting for release. 

I am closing this bug as duplicate of bug 583867.

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