Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1506043

Summary: Subscription-manager segfaults when collecting facts
Product: Red Hat Enterprise Linux 7 Reporter: Paul Dudley <pdudley>
Component: python-dmidecodeAssignee: Petr Oros <poros>
Status: CLOSED DUPLICATE QA Contact: Mike Gahagan <mgahagan>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.4CC: bcourt, pdudley
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-06 10:03:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Paul Dudley 2017-10-24 22:01:15 UTC 
Description of problem:
Susbcription-manager segfaults upon run:

[root@system~]# subscription-manager register --org="Org" --activationkey="Key"
Segmentation fault

Upon looking further it seems the cause of the segfault is during the generation of system facts:

[root@system~]# subscription-manager facts
Segmentation fault

Version-Release number of selected component (if applicable):
[root@system ~]# rpm -q python-rhsm subscription-manager python-rhsm-certificates
python-rhsm-1.19.9-1.el7.x86_64
subscription-manager-1.19.21-1.el7.x86_64
python-rhsm-certificates-1.19.9-1.el7.x86_64

How reproducible:
Reproducible on all customer physical systems of same type

Additional info:

This may be because of the output from dmidecode: 

~~~
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
        Vendor: <BAD INDEX>
        Version: <BAD INDEX>
        Release Date: <BAD INDEX>
        Address: 0xF0000
        Runtime Size: 64 kB
        ROM Size: 4096 kB
        Characteristics:
....

Handle 0x2020, DMI type 32, 32 bytes
System Boot Information
        Status: <OUT OF SPEC>

Handle 0x0100, DMI type 1, 27 bytes
System Information
        Manufacturer: <BAD INDEX>
        Product Name: <BAD INDEX>
        Version: Not Specified
        Serial Number: <BAD INDEX>
        UUID: 4C4C4544-0035-5110-8030-C2C04F545331
        Wake-up Type: Power Switch
        SKU Number: Not Specified
        Family: Not Specified

Handle 0x2020, DMI type 32, 32 bytes

System Boot Information
        Status: <OUT OF SPEC>

Handle 0x0100, DMI type 1, 27 bytes
System Information
        Manufacturer: <BAD INDEX>
        Product Name: <BAD INDEX>
        Version: Not Specified
        Serial Number: <BAD INDEX>
        UUID: 4C4C4544-0035-5110-8030-C2C04F545331
        Wake-up Type: Power Switch
        SKU Number: Not Specified
        Family: Not Specified

Handle 0x2020, DMI type 32, 32 bytes
System Boot Information
        Status: <OUT OF SPEC>

Handle 0x0200, DMI type 2, 9 bytes
Base Board Information
        Manufacturer: <BAD INDEX>
        Product Name: <BAD INDEX>
        Version: <BAD INDEX>
        Serial Number: <BAD INDEX>
        Asset Tag: Not Specified

Handle 0x0300, DMI type 3, 21 bytes
Chassis Information
        Manufacturer: <BAD INDEX>
        Type: Rack Mount Chassis
        Lock: Present
        Version: Not Specified
        Serial Number: <BAD INDEX>
        Asset Tag: Not Specified
        Boot-up State: Safe
        Power Supply State: Safe
        Thermal State: Safe
        Security Status: Unknown
        OEM Information: 0x00000000
        Height: 2 U
        Number Of Power Cords: Unspecified
        Contained Elements: 0
.....
Wrong DMI structures length: 5097 bytes announced, structures occupy 4709 bytes.
~~~
Comment 4 Petr Oros 2017-10-30 09:16:10 UTC 
Please, can you provide DMI table dump?
You can collect it with this command:

$dmidecode --dump-bin output

Thanks,
-Petr
Comment 6 Paul Dudley 2017-11-03 18:02:56 UTC 
Hi!

With further troubleshooting we found the following:

# python -c  "import dmidecode; print dmidecode.bios()"
Segmentation fault

So we reinstalled the package that provides this module:
# rpm -e python-dmidecode
# rpm -Uvh python-dmidecode-3.12.2-1.el7.x86_64.rpm

After this the python -c did not produce a segmentation fault and subscription-manager could run facts just fine.

The version of python-dmidecode did not change and this package had to be reinstalled on multiple physical systems.

It may not be the case that dmidecode is directly responsible for this.

Hope this helps, and thanks!
Paul
Comment 7 Petr Oros 2017-11-06 10:03:00 UTC 

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