Project

General

Profile

Bug #19929

Lock release requests not honored after watch is re-acquired

Added by Jason Dillaman 2 months ago. Updated 2 months ago.

Status:
Pending Backport
Priority:
Normal
Target version:
-
Start date:
05/15/2017
Due date:
% Done:

0%

Source:
Tags:
Backport:
kraken,jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Release:
Needs Doc:
No

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.


Related issues

Copied to rbd - Backport #19957: jewel: rbd: Lock release requests not honored after watch is re-acquired Need More Info
Copied to rbd - Backport #20005: kraken: Lock release requests not honored after watch is re-acquired Need More Info

History

#1 Updated by Jason Dillaman 2 months ago

  • Status changed from In Progress to Need Review

#2 Updated by Mykola Golub 2 months ago

  • Status changed from Need Review to Pending Backport

#3 Updated by Alexey Sheplyakov 2 months ago

  • Copied to Backport #19957: jewel: rbd: Lock release requests not honored after watch is re-acquired added

#4 Updated by Nathan Cutler 2 months ago

  • Copied to Backport #20005: kraken: Lock release requests not honored after watch is re-acquired added

Also available in: Atom PDF