Bug 1439355
| Summary: | [librbd] is_exclusive_lock_owner doesn't detect that is has been blacklisted | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Jason Dillaman <jdillama> |
| Component: | RBD | Assignee: | Jason Dillaman <jdillama> |
| Status: | CLOSED ERRATA | QA Contact: | ceph-qe-bugs <ceph-qe-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.3 | CC: | ceph-eng-bugs, ceph-qe-bugs, hnallurv, jdillama, kdreyer |
| Target Milestone: | rc | Keywords: | CodeChange |
| Target Release: | 2.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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 13:31:40 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jason Dillaman
2017-04-05 19:17:45 UTC
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 |