Bug 1867127 - FFWD2 13->16 livemigration fails on newer CPUs due to arch-facilities vs arch-capabilities
Summary: FFWD2 13->16 livemigration fails on newer CPUs due to arch-facilities vs arch...
Keywords:
Status: CLOSED DUPLICATE of bug 1867128
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 16.1 (Train)
Hardware: x86_64
OS: Unspecified
urgent
urgent
Target Milestone: zstream
: ---
Assignee: Lukas Bezdicka
QA Contact: David Rosenfeld
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-07 12:12 UTC by Lukas Bezdicka
Modified: 2020-08-07 12:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-07 12:49:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lukas Bezdicka 2020-08-07 12:12:55 UTC
Description of problem:
During the final step of FFWD2 the live migration fails to migrate instances from OSP13 EL7.8 hybrid state to OSP16.1 compute with the error:

ERROR nova.virt.libvirt.driver [...] CPU doesn't have compatibility.
internal error: Unknown CPU feature arch-facilities

This is due to RHEL7 naming the feature 'arch-facilities' vs RHEL8 naming the feature 'arch-capabilities'.

A suggested workaround is to remove the 'arch-facilities' feature from /usr/share/libvirt/cpu_map.xml in the libvirt container on the RHEL7 source when switching it into hybrid mode.

While a workaround through documentation is possible, the process to do this is better handled through automation to prevent mistakes.

Comment 1 Kashyap Chamarthy 2020-08-07 12:42:39 UTC
To be more precise, the workaround:

1. On the El-7 host, double-check none of the EL7 instance XML contain 
  'arch-facilities' CPU feature.  Normally, the guests do _not_ have it.

2. Run `virsh capabilities | grep arch-facilities` — it will be present.

3. Comment out 'arch-facilities' in /usr/share/libvirt/cpu_share.xml

4. Restart 'libvirtd' and 'nova-compute' service (both are needed).

5. Then run `virsh capabilities`, again: it will now be absent
   (expected).
   
6. Now migrate the guest from EL7 to EL8: it must succeed.


(Thanks: Jiri Denemark from libvirt team.)

Comment 2 Jesse Pretorius 2020-08-07 12:49:10 UTC

*** This bug has been marked as a duplicate of bug 1867128 ***


Note You need to log in before you can comment on or make changes to this bug.