Actions
Bug #16329
closedrbd-mirror: gracefully handle missing sync point snapshots
Status:
Resolved
Priority:
High
Assignee:
Jason Dillaman
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
If the sync point snapshot for an image being bootstrapped is deleted and the bootstrap is restarted, the bootstrap state machine will see the existing sync point record and associated snapshot name, but it doesn't validate that the snapshot actually exists. If the snapshot doesn't exist, it can lead to an assertion failure since there should always be at least one snapshot to sync from remote to local image.
Updated by Jason Dillaman almost 8 years ago
- Status changed from New to In Progress
- Assignee set to Jason Dillaman
Updated by Jason Dillaman almost 8 years ago
- Status changed from In Progress to Fix Under Review
Updated by Jason Dillaman almost 8 years ago
- Subject changed from rbd-mirror: gracefully handling missing sync point snapshots to rbd-mirror: gracefully handle missing sync point snapshots
Updated by Jason Dillaman almost 8 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to jewel
Updated by Nathan Cutler almost 8 years ago
- Copied to Backport #16373: jewel: rbd-mirror: gracefully handle missing sync point snapshots added
Updated by Loïc Dachary over 7 years ago
- Status changed from Pending Backport to Resolved
Actions