Summary: | use "Red Hat" manufacturer in SMBIOS for RHV VMs | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Michal Skrivanek <michal.skrivanek> |
Component: | rhvm-setup-plugins | Assignee: | Michal Skrivanek <michal.skrivanek> |
Status: | CLOSED ERRATA | QA Contact: | Ryan Barry <rbarry> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | ahadas, lsurette, mavital, michal.skrivanek, mtessun, ratamir, rbarry, Rhev-m-bugs, sgoodman |
Target Milestone: | ovirt-4.2.7 | Keywords: | Regression, ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rhvm-setup-plugins-4.2.12-1.el7ev | Doc Type: | If docs needed, set a value |
Doc Text: |
In Red Hat Virtualization 4.2, the SMBIOS manufacturer was incorrectly identified as "oVirt" when the virtual machine booted. Now it shows "Red Hat".
|
Story Points: | --- |
Clone Of: | 1631360 | Environment: | |
Last Closed: | 2018-11-05 15:04:31 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Bug Depends On: | |||
Bug Blocks: | 1631360, 1634738 |
Description
Michal Skrivanek
2018-09-20 12:14:25 UTC
it's RHEV in the Origin field, and Red Hat in the guest, aligning the title with the original bug Verified on: ovirt-engine-4.2.7.3-0.1.el7ev.noarch.rpm rhvm-4.2.7.3-0.1.el7ev.noarch.rpm If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field. The documentation team will review, edit, and approve the text. If this bug does not require doc text, please set the 'requires_doc_text' flag to -. Michal, Please review my text edits to make sure it is technically correct. LGTM after "BIOS" is changed to "SMBIOS" Done. 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-2018:3489 |