Bug #18435
[ FAILED ] TestLibRBD.RenameViaLockOwner
Status:
Resolved
Priority:
Low
Assignee:
Jason Dillaman
Target version:
-
% Done:
0%
Source:
Q/A
Tags:
Backport:
luminous,jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
When injecting socket failures, if a socket failure results in multiple (duplicate) rename requests to the lock owner, the lock owner doesn't no-op the duplicate rename requests. This results in the rename request failing because it wasn't able to read the "rbd_id.<original image name>" object.
Related issues
History
#1 Updated by Jason Dillaman about 7 years ago
- Status changed from New to In Progress
- Assignee set to Jason Dillaman
#2 Updated by Jason Dillaman over 6 years ago
- Status changed from In Progress to New
#3 Updated by Jason Dillaman over 6 years ago
- Status changed from New to In Progress
- Backport set to luminous,jewel
#4 Updated by Jason Dillaman over 6 years ago
- Status changed from In Progress to Fix Under Review
#5 Updated by Mykola Golub over 6 years ago
- Status changed from Fix Under Review to Pending Backport
#6 Updated by Nathan Cutler about 6 years ago
- Copied to Backport #22593: luminous: [ FAILED ] TestLibRBD.RenameViaLockOwner added
#7 Updated by Nathan Cutler about 6 years ago
- Copied to Backport #22594: jewel: [ FAILED ] TestLibRBD.RenameViaLockOwner added
#8 Updated by Nathan Cutler about 6 years ago
- Status changed from Pending Backport to Resolved