Back to bug 2140988
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Amit Uniyal | 2022-11-08 10:40:44 UTC | Target Release | --- | 17.1 |
| Amit Uniyal | 2022-11-08 10:42:57 UTC | CC | smooney | |
| Amit Uniyal | 2022-11-08 11:02:04 UTC | Status | NEW | ON_DEV |
| RHEL Program Management | 2022-11-08 12:16:16 UTC | Target Release | 17.1 | --- |
| OSP Segritary bot - https://gitlab.cee.redhat.com/osp-dfg-compute/segritary/ | 2022-11-08 13:02:15 UTC | Keywords | Patch | |
| Red Hat One Jira (issues.redhat.com) | 2022-11-08 13:34:34 UTC | Link ID | Red Hat Issue Tracker OSP-19987 | |
| Amit Uniyal | 2022-11-09 07:02:53 UTC | Assignee | nova-maint | auniyal |
| Sylvain Bauza | 2022-11-09 17:12:40 UTC | Severity | unspecified | medium |
| Priority | unspecified | medium | ||
| Keywords | Triaged | |||
| Amit Uniyal | 2023-01-30 06:17:51 UTC | Summary | Update instance host and task state when post live migration fails | Update instance host and task state when post live migration fails - 17.1 |
| Version | 13.0 (Queens) | 17.1(Wallaby) | ||
| Amit Uniyal | 2023-01-30 06:18:36 UTC | Status | ON_DEV | MODIFIED |
| Amit Uniyal | 2023-01-30 06:20:51 UTC | Summary | Update instance host and task state when post live migration fails - 17.1 | 17.1 - Update instance host and task state when post live migration fails |
| Artom Lifshitz | 2023-01-31 16:06:37 UTC | CC | alifshit | |
| Fixed In Version | openstack-nova-23.2.3-1.20230112160825.4f9a306.el9osttrunk | |||
| Artom Lifshitz | 2023-01-31 16:07:38 UTC | Target Milestone | --- | ga |
| RHEL Program Management | 2023-01-31 16:07:48 UTC | Target Release | --- | 17.1 |
| Lon Hohberger | 2023-02-01 07:01:16 UTC | Fixed In Version | openstack-nova-23.2.3-1.20230112160825.4f9a306.el9osttrunk | openstack-nova-23.2.3-1.20230112160825.4f9a306.el9ost |
| errata-xmlrpc | 2023-02-01 17:07:22 UTC | Status | MODIFIED | ON_QA |
| Artom Lifshitz | 2023-03-21 19:59:31 UTC | QA Contact | nova-maint | osp-dfg-compute |
| Andy Stillman | 2023-05-31 21:04:30 UTC | Flags | needinfo?(auniyal) | |
| Artom Lifshitz | 2023-06-02 00:45:08 UTC | Doc Text | Cause: The post live migration operation could fail on the destination compute host before the instance record was updated to record the fact that the instance was now irrevocably running on the host. Consequence: The instance's libvirt domain was running on the destination host, but the instance's record in the database was still set to the source host. The can lead to multiple serious problems if other operations are attempted on the instance. Fix: Always set the instance's host value in the database to the destination host, regardless of other errors. Result: The instance is correctly recorded as running on the destination host in the database. | |
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Amit Uniyal | 2023-06-06 18:37:05 UTC | Flags | needinfo?(auniyal) | needinfo- |
| Amit Uniyal | 2023-06-06 18:39:49 UTC | Flags | needinfo- | |
| Irina | 2023-06-07 10:38:22 UTC | CC | igallagh | |
| Doc Text | Cause: The post live migration operation could fail on the destination compute host before the instance record was updated to record the fact that the instance was now irrevocably running on the host. Consequence: The instance's libvirt domain was running on the destination host, but the instance's record in the database was still set to the source host. The can lead to multiple serious problems if other operations are attempted on the instance. Fix: Always set the instance's host value in the database to the destination host, regardless of other errors. Result: The instance is correctly recorded as running on the destination host in the database. | Before this update, the operations required to complete a live migration could fail because the instance record in the database was not updated to record that the instance was now running on the destination host. With this update, the instance host value in the database is always set to the destination host during live migration. |
||
| Irina | 2023-06-12 09:30:52 UTC | Doc Text | Before this update, the operations required to complete a live migration could fail because the instance record in the database was not updated to record that the instance was now running on the destination host. With this update, the instance host value in the database is always set to the destination host during live migration. | Before this update, the operations required to complete a live migration could fail because the instance record in the database was not updated to record that the instance was now running on the destination host. + With this update, the instance host value in the database is always set to the destination host during live migration. |
| mgeary | 2023-06-14 14:45:56 UTC | Doc Text | Before this update, the operations required to complete a live migration could fail because the instance record in the database was not updated to record that the instance was now running on the destination host. + With this update, the instance host value in the database is always set to the destination host during live migration. | Before this update, a live migration might fail because the database did not update with the destination host details. + With this update, the instance host value in the database is set to the destination host during live migration. |
| CC | mgeary | |||
| errata-xmlrpc | 2023-08-16 00:04:00 UTC | Status | ON_QA | RELEASE_PENDING |
| errata-xmlrpc | 2023-08-16 01:12:28 UTC | Resolution | --- | ERRATA |
| Status | RELEASE_PENDING | CLOSED | ||
| Last Closed | 2023-08-16 01:12:28 UTC | |||
| errata-xmlrpc | 2023-08-16 01:12:52 UTC | Link ID | Red Hat Product Errata RHEA-2023:4577 |
Back to bug 2140988