Back to bug 2116600
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| melanie witt | 2022-08-09 02:20:50 UTC | Keywords | Triaged | |
| RHEL Program Management | 2022-08-09 02:23:39 UTC | Target Release | --- | 17.1 |
| Red Hat One Jira (issues.redhat.com) | 2022-08-09 02:32:48 UTC | Link ID | Red Hat Issue Tracker OSP-18112 | |
| melanie witt | 2022-08-09 07:08:48 UTC | Depends On | 2116679 | |
| melanie witt | 2022-08-09 07:20:32 UTC | Depends On | 2088713 | |
| melanie witt | 2022-09-13 02:18:24 UTC | Link ID | OpenStack gerrit 852002 | |
| melanie witt | 2022-09-13 02:21:41 UTC | Keywords | Patch | |
| Status | ASSIGNED | ON_DEV | ||
| melanie witt | 2022-12-01 22:44:36 UTC | Status | ON_DEV | MODIFIED |
| Fixed In Version | openstack-nova-23.2.2-1.20221121201130.a9e8162.el9osttrunk | |||
| Lon Hohberger | 2022-12-02 07:02:30 UTC | Fixed In Version | openstack-nova-23.2.2-1.20221121201130.a9e8162.el9osttrunk | openstack-nova-23.2.2-1.20221124091252.a9e8162.el9ost |
| errata-xmlrpc | 2022-12-14 10:10:52 UTC | Status | MODIFIED | ON_QA |
| Artom Lifshitz | 2023-03-21 19:56:52 UTC | QA Contact | nova-maint | osp-dfg-compute |
| Andy Stillman | 2023-05-31 21:04:30 UTC | Flags | needinfo?(mwitt) | |
| melanie witt | 2023-06-07 17:28:55 UTC | Doc Type | If docs needed, set a value | Bug Fix |
| Doc Text | Cause: Sometimes during a live migration, a libvirt internal error "migration was active, but no RAM info was set" is raised even though the live migration was successful. Consequence: The live migration failed when it should have succeeded. Fix: When libvirt internal error "migration was active, but no RAM info was set" is raised, signal the live migration as complete in the libvirt driver. Result: The live migration will correctly succeed in this condition. |
|||
| melanie witt | 2023-06-07 17:29:39 UTC | Flags | needinfo?(mwitt) | |
| Jenny-Anne Lynch | 2023-06-08 08:40:15 UTC | CC | jelynch | |
| Doc Text | Cause: Sometimes during a live migration, a libvirt internal error "migration was active, but no RAM info was set" is raised even though the live migration was successful. Consequence: The live migration failed when it should have succeeded. Fix: When libvirt internal error "migration was active, but no RAM info was set" is raised, signal the live migration as complete in the libvirt driver. Result: The live migration will correctly succeed in this condition. | Sometimes, during a live migration, a libvirt internal error `migration was active, but no RAM info was set` was raised even though the live migration was successful. The live migration failed when it should have succeeded. With this update, when this libvirt internal error is raised, the live migration is signalled as complete in the libvirt driver. The live migration correctly succeeds in this condition. | ||
| Joanne O'Flynn | 2023-06-12 10:09:44 UTC | CC | joflynn | |
| Doc Text | Sometimes, during a live migration, a libvirt internal error `migration was active, but no RAM info was set` was raised even though the live migration was successful. The live migration failed when it should have succeeded. With this update, when this libvirt internal error is raised, the live migration is signalled as complete in the libvirt driver. The live migration correctly succeeds in this condition. | Sometimes, during a live migration, a libvirt internal error `migration was active, but no RAM info was set` was raised even though the live migration was successful. The live migration failed 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. The live migration correctly succeeds in this condition. | ||
| Lukas Svaty | 2023-06-16 08:13:29 UTC | Target Milestone | beta | ga |
| Jenny-Anne Lynch | 2023-07-19 12:19:16 UTC | CC | jelynch | |
| errata-xmlrpc | 2023-08-16 00:03:13 UTC | Status | ON_QA | RELEASE_PENDING |
| errata-xmlrpc | 2023-08-16 01:11:45 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2023-08-16 01:11:45 UTC | |||
| errata-xmlrpc | 2023-08-16 01:12:13 UTC | Link ID | Red Hat Product Errata RHEA-2023:4577 | |
| Irina | 2023-08-17 13:32:58 UTC | Doc Text | Sometimes, during a live migration, a libvirt internal error `migration was active, but no RAM info was set` was raised even though the live migration was successful. The live migration failed 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. The live migration correctly succeeds in this condition. | 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. |
| CC | igallagh |
Back to bug 2116600