Bug 2074219 - while live-migrating many instances concurrently, libvirt sometimes return internal error: migration was active, but no RAM info was set
Summary: while live-migrating many instances concurrently, libvirt sometimes return in...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 16.1 (Train)
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: z10
: 16.1 (Train on RHEL 8.2)
Assignee: melanie witt
QA Contact: OSP DFG:Compute
URL:
Whiteboard:
Depends On: 2074205 2088676 2161781 2161784 2168214
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-11 19:19 UTC by David Hill
Modified: 2024-01-15 16:02 UTC (History)
11 users (show)

Fixed In Version: openstack-nova-20.4.1-1.20221121203755.1ee93b9.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2074205
: 2088676 (view as bug list)
Environment:
Last Closed: 2024-01-15 16:02:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 837323 0 None NEW libvirt: Abort live-migration job when monitoring fails 2022-04-11 19:25:38 UTC
OpenStack gerrit 852002 0 None NEW Handle "no RAM info was set" migration case 2022-09-13 02:20:06 UTC
Red Hat Issue Tracker OSP-14627 0 None None None 2022-04-11 19:24:13 UTC
Red Hat Knowledge Base (Solution) 6903451 0 None None None 2022-04-11 19:21:10 UTC

Comment 1 David Hill 2022-04-11 19:22:57 UTC 
This is a clone of the libvirtd bug but I've found a commit in master that would avoid customer's main issue of VMs being stuck in-between two computes in regards to the database.  We need that fix in nova-compute.
Comment 4 Artom Lifshitz 2024-01-15 16:02:08 UTC 
Given that we've stopped doing 16.2 maintenance releases, the chances of a 16.1 MR are basically none at this point. Closing EOL.
Note You need to log in before you can comment on or make changes to this bug.