Project

General

Profile

Bug #19287

[api] is_exclusive_lock_owner doesn't detect that is has been blacklisted

Added by Jason Dillaman 4 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Target version:
-
Start date:
03/16/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

If the exclusive lock is stolen by another client which resulted in the blacklisting of the current client, this helper method should return -ESHUTDOWN (-EBLACKLISTED internally) instead of 0.


Related issues

Copied to rbd - Backport #19467: kraken: [api] is_exclusive_lock_owner doesn't detect that is has been blacklisted Resolved
Copied to rbd - Backport #19468: jewel: [api] is_exclusive_lock_owner doesn't detect that is has been blacklisted Resolved

History

#1 Updated by Jason Dillaman 4 months ago

  • Status changed from In Progress to Need Review

#2 Updated by Mykola Golub 4 months ago

  • Status changed from Need Review to Pending Backport

#3 Updated by Nathan Cutler 4 months ago

  • Copied to Backport #19467: kraken: [api] is_exclusive_lock_owner doesn't detect that is has been blacklisted added

#4 Updated by Nathan Cutler 4 months ago

  • Copied to Backport #19468: jewel: [api] is_exclusive_lock_owner doesn't detect that is has been blacklisted added

#5 Updated by Nathan Cutler 3 months ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF