Actions
Bug #19459
closedsnap rollback failed after rbd client exited or osd rebooted abnornally
Status:
Won't Fix
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
If snap rollback was interrupted by rbd client exited or osd rebooted abnornally.
the users would run a new rbd client and snap rollback fail after the osd restore, it prompt error "Read-Only", then after 30s, the user would try again and succeed.
Updated by Jason Dillaman almost 7 years ago
- Status changed from New to Won't Fix
This is the expected behavior when using the exclusive lock functionality.
Actions