Actions
Bug #41394
closed[migration] using abort can result in the loss of data
Status:
Resolved
Priority:
Normal
Assignee:
Jason Dillaman
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
nautilus,octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
If the migration destination image has been written against, running "rbd migration abort" will not copy the new data back to the source image. If it's not feasible to support a live-migrate abort, force it to be an offline process.
Updated by Jason Dillaman over 3 years ago
- Status changed from New to In Progress
- Assignee set to Jason Dillaman
- Backport changed from nautilus to nautilus,octopus
Updated by Jason Dillaman over 3 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 36471
Updated by Mykola Golub over 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #47099: octopus: [migration] using abort can result in the loss of data added
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #47100: nautilus: [migration] using abort can result in the loss of data added
Updated by Nathan Cutler over 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions