Bug 1624453
| Summary: | Host "hostname" moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : ssbd, spec_ctrl | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Frank DeLorey <fdelorey> |
| Component: | rhev-hypervisor-ng | Assignee: | Yuval Turgeman <yturgema> |
| Status: | CLOSED ERRATA | QA Contact: | Huijuan Zhao <huzhao> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.2.5 | CC: | cshao, dfediuck, fdelorey, kmashalk, lsurette, michal.skrivanek, mkalinin, pstehlik, rbarry, sbonazzo, srevivo, ycui, yturgema |
| Target Milestone: | ovirt-4.2.7 | Keywords: | Reopened, TestOnly, ZStream |
| Target Release: | --- | Flags: | lsvaty:
testing_plan_complete-
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-22 08:30:37 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: | |||
| Bug Blocks: | 1547768 | ||
|
Description
Frank DeLorey
2018-08-31 15:59:53 UTC
This is not related to RHVH. We don't touch these profiles. Can you please capture cpuinfo and virsh capabilities before and after the upgrade so I can move to the appropriate team? I'm not sure whether this is ovirt-engine or libvirt, since comments on https://bugzilla.redhat.com/show_bug.cgi?id=1584219 indicate that libvirt may cache microcode "forever", and microcode changes may need a cache flush Flags show it’s not running recent enough firmware and it doesn’t support spec_ctrl nor ssbd. Can you add the same output from the same host when running rhvh-4.2.4.3-0.20180622? Microcode versions differ. Are they really the same host? How’s that possible? QE can reproduce this issue. Test version: rhvh-4.2.4.3-0.20180622. rhvh-4.2.5.2-0.20180813 rhv-4.2.6-4 Test steps: 1. Install rhvh-4.2.4.3-0.20180622. 2. Register to engine. 3. Upgrade to rhvh-4.2.5.2-0.20180813 via RHVM GUI. Test result: Host "hostname" moved to Non-Operational state as host does not meet the cluster's minimum CPU level. Missing CPU features : spec_ctrl (In reply to cshao from comment #17) > Test steps: > 1. Install rhvh-4.2.4.3-0.20180622. > 2. Register to engine. > 3. Upgrade to rhvh-4.2.5.2-0.20180813 via RHVM GUI. > > Test result: > Host "hostname" moved to Non-Operational state as host does not meet the > cluster's minimum CPU level. Missing CPU features : spec_ctrl Chen, can you please try to reproduce with latest released 4.2.6 RHV-H? If microcode_ctl related, 4.2.6 should have the right one included. (In reply to Sandro Bonazzola from comment #18) > (In reply to cshao from comment #17) > > > Test steps: > > 1. Install rhvh-4.2.4.3-0.20180622. > > 2. Register to engine. > > 3. Upgrade to rhvh-4.2.5.2-0.20180813 via RHVM GUI. > > > > Test result: > > Host "hostname" moved to Non-Operational state as host does not meet the > > cluster's minimum CPU level. Missing CPU features : spec_ctrl > > Chen, can you please try to reproduce with latest released 4.2.6 RHV-H? > If microcode_ctl related, 4.2.6 should have the right one included. Can't reproduce this issue with latest released 4.2.6 RHV-H. Test version: Upgrade from rhvh-4.2.4.3-0.20180622 to: RHVH 4.2.6 async - rhvh-4.2.6.1-0.20180907.0+1 to: RHVH 4.2.7 - rhvh-4.2.7.0-0.20180918.0+1 Test steps: 1. Install rhvh-4.2.4.3-0.20180622. 2. Register to engine. 3. Upgrade to 4.2.6 / 4.2.7 via RHVM GUI. Test result: Upgrade can succeed, RHVH can up. 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://access.redhat.com/errata/RHSA-2018:3470 sync2jira sync2jira |