Bug 1652519
Summary: | host does not meet the cluster's minimum CPU level. Missing CPU features : spec_ctrl | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Kumar Mashalkar <kmashalk> |
Component: | redhat-virtualization-host | Assignee: | Yuval Turgeman <yturgema> |
Status: | CLOSED ERRATA | QA Contact: | Huijuan Zhao <huzhao> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.2.7 | CC: | cshao, dfediuck, huzhao, kmashalk, lsvaty, michal.skrivanek, nlevy, qiyuan, rbarry, rdlugyhe, rhodain, sbonazzo, sirao, weiwang, yaniwang, ycui, yturgema |
Target Milestone: | ovirt-4.3.1 | ||
Target Release: | 4.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, during an upgrade, dracut running inside chroot did not detect the cpuinfo and the kernel config files because /proc was not mounted and /boot was bindmounted. As a result, the correct microcode was missing from the initramfs.
The current release bindmounts /proc to the chroot and removes the --hostonly flag. This change inserts both AMD and Intel microcodes into the initramfs and boots the host after an upgrade.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-08 12:32:19 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: |
Description
Kumar Mashalkar
2018-11-22 09:38:57 UTC
You need to add same details and investigate similarly to the original bug. Otherwise this report is kind of unhelpful. Also please add sql dump of the corresponding host and cluster tables. Thanks To follow up, please provide, at a minimum, the output of lscpu, a sql dump or screenshot of the cluster CPU level, and the host CPU details as reported by RHVM it's still the same thing, the CPU is plain Haswell-noTSX without any microcode update (record 3 in your list seems to be updated, record 4 does not) rhvh 4.2.7 ships with microcode_ctl-2.1-47.el7.x86_64, which should be up to date unless some change in 7.6 disabled default mitigation. Please post dmesg and the output of /proc/cmdline Additionally, please ensure that 'rpm -q microcode_ctl' shows the version above you still do not have the latest microcode applied (running 0x38), AFAICT the latest in that microcode_ctl is 0x3d. Ryan, is it possible it's wrong in the dracut image of rhvh? The microcode_ctl version look ok, it's just not getting applied it seems. It's possible, but would require user intervention. Kumar, can the custoemr please try unpacking the initrd to verify the firmware files present? Moving back to Node, since the engine is doing what it's supposed to be doing cshao@ reproduced this issue in https://bugzilla.redhat.com/show_bug.cgi?id=1624453#c17 But with the same rhvh version(from rhvh-4.2.4.3-0.20180622 to rhvh-4.2.5.2-0.20180813), I did not reproduce this issue with rhvm-4.2.7.5-0.1.el7ev, maybe related to the old rhvm-4.2.5 then. According to https://bugzilla.redhat.com/show_bug.cgi?id=1624453#c17, QE will flag qa_ack+ Moving to 4.3.2 not being identified as blocker for 4.3.1 The bug is fixed in rhvh-4.3.0.5-0.20190225.0 with rhvm-4.2.8.2-0.1.el7ev Test version: # imgbase layout rhvh-4.2.4.3-0.20180622.0 +- rhvh-4.2.4.3-0.20180622.0+1 rhvh-4.3.0.5-0.20190225.0 +- rhvh-4.3.0.5-0.20190225.0+1 Test steps: 1. Install rhvh-4.2.4.3-0.20180622.0 2. Add rhvh to rhvm 3. Upgrade rhvh to rhvh-4.3.0.5-0.20190225.0 from rhvm side Test results: After step 3, rhvh is active in rhvm Moving 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://access.redhat.com/errata/RHBA-2019:1053 sync2jira sync2jira |