Description of problem: The librbd API's "is_exclusive_lock_owner" does not properly detect when a client has been blacklisted. Version-Release number of selected component (if applicable): 2.2 How reproducible: 100% Steps to Reproduce: 1. use the API directly 2. acquire exclusive lock on image 3. blacklist image 4. test exclusive lock ownership status Actual results: API doesn't detect the blacklist and loss of exclusive lock Expected results: API should detect that is was blacklisted Additional info:
This fix is required for low-level RBD/iSCSI integration via TCMU
(In reply to Jason Dillaman from comment #0) > Description of problem: > The librbd API's "is_exclusive_lock_owner" does not properly detect when a > client has been blacklisted. > > Version-Release number of selected component (if applicable): > 2.2 > > How reproducible: > 100% > > Steps to Reproduce: > 1. use the API directly > 2. acquire exclusive lock on image > 3. blacklist image > 4. test exclusive lock ownership status > > Actual results: > API doesn't detect the blacklist and loss of exclusive lock > > Expected results: > API should detect that is was blacklisted > > Additional info: @Jason, Can you please share the procedure to blacklist the image?
@Vidushi: this BZ was flagged as CodeChange since it really isn't testable (since it requires using the API directly).
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1497