Bug 1439355 – [librbd] is_exclusive_lock_owner doesn't detect that is has been blacklisted

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1439355 - [librbd] is_exclusive_lock_owner doesn't detect that is has been blacklisted

Summary:	[librbd] is_exclusive_lock_owner doesn't detect that is has been blacklisted

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Ceph Storage
Classification:	Red Hat
Component:	RBD (Show other bugs)
Sub Component:
Version:	2.3
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	2.3
Assigned To:	Jason Dillaman
QA Contact:	ceph-qe-bugs
Docs Contact:

URL:
Whiteboard:
Keywords:	CodeChange

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-04-05 15:17 EDT by Jason Dillaman
Modified:	2017-07-30 11:36 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:	RHEL: ceph-10.2.7-3.el7cp Ubuntu: ceph_10.2.7-4redhat1xenial
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-06-19 09:31:40 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Ceph Project Bug Tracker	19468	None	None	None	2017-04-05 15:17 EDT
Red Hat Product Errata	RHBA-2017:1497	normal	SHIPPED_LIVE	Red Hat Ceph Storage 2.3 bug fix and enhancement update	2017-06-19 13:24:11 EDT

Groups: None (edit)

Description Jason Dillaman 2017-04-05 15:17:45 EDT

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:

Comment 2 Jason Dillaman 2017-04-05 15:18:54 EDT

This fix is required for low-level RBD/iSCSI integration via TCMU

Comment 7 vidushi 2017-05-23 07:11:46 EDT

(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?

Comment 8 Jason Dillaman 2017-05-23 09:45:37 EDT

@Vidushi: this BZ was flagged as CodeChange since it really isn't testable (since it requires using the API directly).

Comment 12 errata-xmlrpc 2017-06-19 09:31:40 EDT

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

Note You need to log in before you can comment on or make changes to this bug.