Back to bug 2193392
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| nijin ashok | 2023-05-05 13:58:36 UTC | Severity | urgent | high |
| Casper (RHV QE bot) | 2023-05-05 14:00:50 UTC | QA Contact | mavital | aefrat |
| nijin ashok | 2023-05-09 05:03:09 UTC | Link ID | Red Hat Knowledge Base (Solution) 7011730 | |
| Michal Skrivanek | 2023-05-18 10:53:33 UTC | CC | michal.skrivanek | |
| Germano Veit Michel | 2023-05-19 03:42:29 UTC | CC | gveitmic | |
| Michal Skrivanek | 2023-05-31 10:53:16 UTC | Flags | needinfo?(gveitmic) | |
| Germano Veit Michel | 2023-05-31 22:55:59 UTC | Flags | needinfo?(gveitmic) | |
| Michal Skrivanek | 2023-06-07 10:49:59 UTC | CC | ahadas | |
| Flags | needinfo?(ahadas) | |||
| Arik | 2023-06-26 19:44:11 UTC | Target Milestone | --- | ovirt-4.5.3-async |
| Assignee | nobody | ahadas | ||
| Flags | needinfo?(ahadas) | |||
| CC | bzlotnik | |||
| Arik | 2023-07-04 10:46:48 UTC | Status | NEW | ASSIGNED |
| Component | ovirt-engine | vdsm | ||
| CC | lsurette, srevivo, ycui | |||
| QA Contact | aefrat | sfishbai | ||
| Arik | 2023-07-04 11:04:14 UTC | Link ID | Github oVirt/vdsm/pull/397 | |
| Status | ASSIGNED | POST | ||
| Arik | 2023-07-23 11:37:47 UTC | Link ID | Github oVirt/vdsm/pull/400 | |
| Arik | 2023-07-25 08:21:32 UTC | Status | POST | MODIFIED |
| RHEL Program Management | 2023-07-25 08:21:41 UTC | Status | MODIFIED | POST |
| Arik | 2023-07-25 08:39:13 UTC | Doc Type | If docs needed, set a value | Bug Fix |
| Status | POST | MODIFIED | ||
| Doc Text | Cause: the LV on the target storage domain was not deactivated when live storage migration failed. Consequence: the LV remained on the target storage domain and that could have led to data corruption when another live storage migration occurs. Fix: when live storage migration fails, VDSM deactivates the LV that was created on the target storage domain. Result: when live storage migration fails, we no longer have remaining of LVs that were created on the target storage domain that could lead to data corruption. |
|||
| errata-xmlrpc | 2023-07-31 12:36:22 UTC | Status | MODIFIED | ON_QA |
| Eli Marcus | 2023-08-15 11:55:37 UTC | CC | emarcus | |
| Doc Text | Cause: the LV on the target storage domain was not deactivated when live storage migration failed. Consequence: the LV remained on the target storage domain and that could have led to data corruption when another live storage migration occurs. Fix: when live storage migration fails, VDSM deactivates the LV that was created on the target storage domain. Result: when live storage migration fails, we no longer have remaining of LVs that were created on the target storage domain that could lead to data corruption. | Previously, the LV on the target storage domain was not deactivated when live storage migration failed. In this release, when live storage migration fails, VDSM deactivates the LV that was created on the target storage domain. |
Back to bug 2193392