Bug 1109342
Summary: | "Invalid dmidecode output" alert upon Host approval | |||
---|---|---|---|---|
Product: | [oVirt] ovirt-host-deploy | Reporter: | Yaniv Bronhaim <ybronhei> | |
Component: | Plugins.VDSM | Assignee: | Alon Bar-Lev <alonbl> | |
Status: | CLOSED ERRATA | QA Contact: | Tareq Alayan <talayan> | |
Severity: | urgent | Docs Contact: | ||
Priority: | urgent | |||
Version: | 1.2.0 | CC: | aberezin, acathrow, adahms, audgiri, bazulay, bugs, dougsland, iheim, jboggs, juzhang, lpeer, oourfali, ovirt-maint, pdwyer, pstehlik, Rhev-m-bugs, ybronhei, yeylon | |
Target Milestone: | --- | Keywords: | ZStream | |
Target Release: | 1.2.2 | Flags: | oourfali:
devel_ack+
|
|
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | infra | |||
Fixed In Version: | ovirt-host-deploy-1.2.2-1.el6ev | Doc Type: | Bug Fix | |
Doc Text: |
Previously, the Red Hat Enterprise Virtualization Manager would report an error with invalid dmidecode output when attempting to approve a hypervisor, with the approval operation completing successfully. This was caused by the logic dmidecode parsing logic, whereby lines prefixed with a '#' - indicating a comment - would be parsed. Now, this logic has been revised so that lines prefixed with '#' are not parsed, preventing this error message from appearing.
|
Story Points: | --- | |
Clone Of: | 1098333 | |||
: | 1111049 (view as bug list) | Environment: | ||
Last Closed: | 2014-07-29 14:07:51 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 739645, 1098333, 1111049 | |||
Bug Blocks: |
Comment 1
Alon Bar-Lev
2014-06-17 19:06:22 UTC
Can some tell why robot does not set the rhevm-3.4.z flag? 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. http://rhn.redhat.com/errata/RHBA-2014-0962.html |