Bug 1096163
| Summary: | An error appeared when view cpu details info | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | cshao <cshao> |
| Component: | ovirt-node | Assignee: | Joey Boggs <jboggs> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.3.0 | CC: | dfediuck, fdeutsch, gklein, gouyang, hadong, huiwa, iheim, jboggs, leiwang, rbarry, sherold, yaniwang, ycui |
| Target Milestone: | --- | ||
| Target Release: | 3.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | node | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-02-11 20:57:10 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1097295 | ||
| Bug Blocks: | |||
|
Description
cshao
2014-05-09 10:27:15 UTC
This should basically be addressed by fixing bug 1062111. Basically we need to get away from th einfos libvirt provides, as libvirt only provides the best fit of the known CPU models based on the cpu flags. The results in incorrect informations if the database is outdated. I could not reproduce this with the latest rhevh7 build, please test and close if fixed. The patch adds an even more reliable way This is a mass change, moving bugs of merged patches into MODIFIED. Please correct the state, if you think that the move was not justified. Test version: rhev-hypervisor7-7.0-20141006.0.el7ev.noarch ovirt-node-3.1.0-0.20.20141006gitc421e04.el7.noarch Test steps: 1. Install rhevh-7.0 2. Enter Status page. 3. Click "View CPU Details" Test result: Can show cpu details info correctly. So the bug is fixed, change bug status to VERIFIED. 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://rhn.redhat.com/errata/RHEA-2015-0160.html |