Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2074219

Summary: while live-migrating many instances concurrently, libvirt sometimes return internal error: migration was active, but no RAM info was set
Product: Red Hat OpenStack Reporter: David Hill <dhill>
Component: openstack-novaAssignee: melanie witt <mwitt>
Status: CLOSED EOL QA Contact: OSP DFG:Compute <osp-dfg-compute>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.1 (Train)CC: alifshit, bgibizer, dasmith, eglynn, jhakimra, kchamart, sbauza, sgordon, virt-bugs, virt-maint, vromanso
Target Milestone: z10Keywords: Patch, Triaged
Target Release: 16.1 (Train on RHEL 8.2)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-nova-20.4.1-1.20221121203755.1ee93b9.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2074205
: 2088676 (view as bug list) Environment:
Last Closed: 2024-01-15 16:02:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2074205, 2088676, 2161781, 2161784, 2168214    
Bug Blocks:    

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.