Actions
Bug #18666
closedPrevent librbd from blacklisting the in-use librados client
Status:
Resolved
Priority:
Normal
Assignee:
Jason Dillaman
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
kraken,jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
While investigating a test failure where the data on the OSDs apparently went back in time (incorrectly), this resulted in a librbd client blacklisting itself because it wasn't able to remove and re-add its exclusive lock since the lock state jumped back to a period of time when the lock was owned by another instance of the client.
Updated by Jason Dillaman over 7 years ago
- Status changed from In Progress to Fix Under Review
Updated by Mykola Golub about 7 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler about 7 years ago
- Copied to Backport #18703: kraken: Prevent librbd from blacklisting the in-use librados client added
Updated by Nathan Cutler about 7 years ago
- Copied to Backport #18704: jewel: Prevent librbd from blacklisting the in-use librados client added
Updated by Nathan Cutler over 6 years ago
- Status changed from Pending Backport to Resolved
Actions