Project

General

Profile

Bug #41394

[migration] using abort can result in the loss of data

Added by Jason Dillaman over 2 years ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jason Dillaman
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
nautilus,octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

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.


Related issues

Copied to rbd - Backport #47099: octopus: [migration] using abort can result in the loss of data Resolved
Copied to rbd - Backport #47100: nautilus: [migration] using abort can result in the loss of data Resolved

History

#1 Updated by Jason Dillaman over 1 year ago

  • Status changed from New to In Progress
  • Assignee set to Jason Dillaman
  • Backport changed from nautilus to nautilus,octopus

#2 Updated by Jason Dillaman over 1 year ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 36471

#3 Updated by Mykola Golub over 1 year ago

  • Status changed from Fix Under Review to Pending Backport

#4 Updated by Nathan Cutler over 1 year ago

  • Copied to Backport #47099: octopus: [migration] using abort can result in the loss of data added

#5 Updated by Nathan Cutler over 1 year ago

  • Copied to Backport #47100: nautilus: [migration] using abort can result in the loss of data added

#6 Updated by Nathan Cutler about 1 year 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".

Also available in: Atom PDF