Red Hat Bugzilla – Bug 460940
'hts discover' is using the BIOS manufacturer name for the system manufactuer
Last modified: 2014-03-25 20:55:31 EDT
(See also Issue-Tracker #216956)
Description of problem:
Running 'hts discover' seems to assume that the BIOS manufacturer is also the system manufacturer, as that is what gets put into the config.xml.
Happens every time
Steps to Reproduce:
1. Run 'hts discover' on a Stratus ftServer (or presumably any system with a different manufacturer than the BIOS)
For the Stratus ftServer, the system manufacturer as written to config.xml is "Phoenix Technologies LTD", who isn't actually the system manufacturer.
I would have expected the system manufacturer to be "Stratus Technologies"
Would it be better if we changed it to have the user verify the information
after we get it from BIOS?
Possibly both. I understand the question of the BIOS maker is almost never the same as the system maker; however most vendors change that field when they build their BIOS from the kit. We should investigate if there is a better product field provided by dmidecode (there may not be). For the best user experience we're probably best off using the dmidecode data to pre-populate a confirmation field which would be the same as the one where dmidecode isn't present on the arch?
Created attachment 347671 [details]
hardwaretest.py patch changing the vendor key from "Vendor" to "Manufacturer"
v7-1.0-14.el5 doesn't include discover option.
Release note added. If any revisions are required, please set the
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.
BIOS manufacturer might not always be the machine manufacturer.
Test suite reports in-correct machine manufacturer.
Changed the vendor key from "Vendor" to "Manufacturer".
Correct machine manufacturer will be reported.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.