Project

General

Profile

Bug #20182

[api] is_exclusive_lock_owner shouldn't return -EBUSY

Added by Jason Dillaman over 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
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:

Description

This error code indicates that another client owns the exclusive lock. Instead, it should return 0 with the boolean set to false.


Related issues

Copied to rbd - Backport #20266: kraken: [api] is_exclusive_lock_owner shouldn't return -EBUSY Resolved
Copied to rbd - Backport #20267: jewel: [api] is_exclusive_lock_owner shouldn't return -EBUSY Resolved

History

#1 Updated by Jason Dillaman over 3 years ago

  • Status changed from In Progress to Fix Under Review

#2 Updated by Mykola Golub over 3 years ago

  • Status changed from Fix Under Review to Pending Backport

#3 Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #20266: kraken: [api] is_exclusive_lock_owner shouldn't return -EBUSY added

#4 Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #20267: jewel: [api] is_exclusive_lock_owner shouldn't return -EBUSY added

#5 Updated by Nathan Cutler about 3 years ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF