Actions
Bug #19929
closedLock release requests not honored after watch is re-acquired
Status:
Resolved
Priority:
Normal
Assignee:
Jason Dillaman
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
After the watch fails, the lock owner client id is cleared and the re-acquire process is started. If the re-acquire is successful (supported by the OSDs), the lock owner client id will never be re-initialized. Since this is used as a guard for release lock request messages, the client in this state will just ACK the release request without actually starting the process.
Updated by Jason Dillaman almost 7 years ago
- Status changed from In Progress to Fix Under Review
Updated by Mykola Golub almost 7 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Alexey Sheplyakov almost 7 years ago
- Copied to Backport #19957: jewel: rbd: Lock release requests not honored after watch is re-acquired added
Updated by Nathan Cutler almost 7 years ago
- Copied to Backport #20005: kraken: Lock release requests not honored after watch is re-acquired added
Updated by Jason Dillaman over 6 years ago
- Backport changed from kraken,jewel to jewel
Updated by Nathan Cutler over 6 years ago
- Copied to deleted (Backport #20005: kraken: Lock release requests not honored after watch is re-acquired)
Updated by Nathan Cutler over 6 years ago
- Status changed from Pending Backport to Resolved
Actions