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 1688314

Summary: need to update dmidecode to version 3.2
Product: Red Hat Enterprise Linux 7 Reporter: Neil Horman <nhorman>
Component: dmidecodeAssignee: lijiang
Status: CLOSED ERRATA QA Contact: Jeff Bastian <jbastian>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.6CC: ruyang, rvr
Target Milestone: rc   
Target Release: 7.7   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dmidecode-3.2-2.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 12:03:23 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:
Bug Depends On:    
Bug Blocks: 1515078, 1661416    

Description Neil Horman 2019-03-13 14:21:22 UTC 
We have a requirement to integrate the redfish-finder package into RHEL7.7, which has a dependency on at least version 3.2 of dmidecode.  Can you please update the package to that version so that we have support for the latest smbios specification, which include interpretation of the Host Management Controller block?
Comment 3 Jeff Bastian 2019-04-22 19:07:55 UTC 
(In reply to Neil Horman from comment #0)
> We have a requirement to integrate the redfish-finder package into RHEL7.7,
> which has a dependency on at least version 3.2 of dmidecode.

See bug 1515078.

Neil, it looks like redfish-finder does not have an rpm requirement on a version:

$ rpm -qp --requires redfish-finder-0.3-1.el7.noarch.rpm | grep dmidecode
dmidecode

Should the rpm requirements be updated to 'dmidecode >= 3.2' ?
Comment 8 Jeff Bastian 2019-04-22 19:22:29 UTC 
(In reply to Jeff Bastian from comment #3) 
> Should the rpm requirements be updated to 'dmidecode >= 3.2' ?

Let's move this discussion to the right place in bug 1515078 comment 22
Comment 9 Jeff Bastian 2019-06-17 15:52:06 UTC 
Verified RHEL-7.7-20190612.0 (Snapshot 3.0) contains dmidecode 3.2:

[root@lenovo-01 ~]# grep -m1 DISTRO /etc/motd
                           DISTRO=RHEL-7.7-20190612.0                             

[root@lenovo-01 ~]# rpm -q dmidecode
dmidecode-3.2-3.el7.x86_64

[root@lenovo-01 ~]# dmidecode -t0
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 3.0 present.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
	Vendor: LENOVO
	Version: S04KT09A
	Release Date: 08/24/2017
        ...
Comment 12 errata-xmlrpc 2019-08-06 12:03:23 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2025