DescriptionKashyap Chamarthy
2022-04-27 15:17:02 UTC
[This bug was initially created as a copy of bug #2076884 (OSP 16.1). This copy is for OSP 16.2.]
Description of problem:
A customer has a 16.1.5 environment with this setup:
- all the compute nodes with tsx=off in cmdline (all with Intel(R) Xeon(R) Gold 6254 CPU @ 3.10GHz stepping=7)
- capabilities file shows the host cpu as: Cascadelake-Server-noTSX
- all the instances running show in their host process the CPU: -cpu Cascadelake-Server
- nova.conf with cpu_mode=host-model
- libvirt 6.0.0-25.5
in this situation live-migration doesn't work with error:
"Unacceptable CPU info: CPU doesn't have compatibility"
Version-Release number of selected component (if applicable):
rhosp 16.1.5
openstack-nova-libvirt:16.1.5-1 container
libvirt 6.0.0-25.5
How reproducible:
all the times
Steps to Reproduce:
1.create a test instance on source compute
2.live migrate instance to destination
3.
Actual results:
live-migration doesn't work with error:
"Unacceptable CPU info: CPU doesn't have compatibility.
0
Refer to http://libvirt.org/html/libvirt-libvirt-host.html#virCPUCompareResult (HTTP 400)"
Expected results:
working live migration.
Additional info:
The customer has another environment with the same setup but on 16.2.1: there live migration works out of the box.
Is there any patch that we can apply on the actual env just to avoid forcing the cpu model in nova (which is working, but it's not serviceable 'cause all the instances need to be rebooted before the live migration)?
Linking the case.
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 (Release of components for Red Hat OpenStack Platform 16.2.4), 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-2022:8794