Bug 2116600
| Summary: | [OSP17.1] 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: | melanie witt <mwitt> | |
| Component: | openstack-nova | Assignee: | melanie witt <mwitt> | |
| Status: | CLOSED ERRATA | QA Contact: | OSP DFG:Compute <osp-dfg-compute> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 17.1 (Wallaby) | CC: | dasmith, eglynn, igallagh, jhakimra, joflynn, kchamart, sbauza, sgordon, vromanso | |
| Target Milestone: | ga | Keywords: | Patch, Triaged | |
| Target Release: | 17.1 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-nova-23.2.2-1.20221124091252.a9e8162.el9ost | Doc Type: | Bug Fix | |
| Doc Text: |
Before this update, the following libvirt internal error was sometimes raised during a successful live migration: "migration was active, but no RAM info was set". This caused the live migration to fail when it should have succeeded. With this update, when this libvirt internal error is raised, the live migration is signaled as complete in the libvirt driver and the live migration correctly succeeds.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 2116679 (view as bug list) | Environment: | ||
| Last Closed: | 2023-08-16 01:11:45 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: | 2088713, 2116679 | |||
| Bug Blocks: | 2088677 | |||
|
Comment 9
Lukas Svaty
2023-06-16 08:13:29 UTC
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 17.1 (Wallaby)), 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/RHEA-2023:4577 |