New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jewel: rbd: api: is_exclusive_lock_owner shouldn't return -EBUSY #16296

Merged
merged 1 commit into from Sep 11, 2017

Conversation

Projects
None yet
2 participants
@smithfarm
Contributor

smithfarm commented Jul 12, 2017

librbd: filter expected error codes from is_exclusive_lock_owner
Fixes: http://tracker.ceph.com/issues/20182
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
(cherry picked from commit d4daaf5)

@smithfarm smithfarm self-assigned this Jul 12, 2017

@smithfarm smithfarm added this to the jewel milestone Jul 12, 2017

@smithfarm smithfarm changed the title from jewel: [api] is_exclusive_lock_owner shouldn't return -EBUSY to jewel: rbd: api: is_exclusive_lock_owner shouldn't return -EBUSY Jul 12, 2017

@smithfarm smithfarm added rbd and removed core labels Jul 12, 2017

@smithfarm smithfarm requested a review from dillaman Sep 10, 2017

@smithfarm

This comment has been minimized.

Show comment
Hide comment
@smithfarm

smithfarm Sep 10, 2017

Contributor

@dillaman This passed an rbd suite at http://tracker.ceph.com/issues/20613#note-59 with one failure that passed on rerun.

Please review.

Contributor

smithfarm commented Sep 10, 2017

@dillaman This passed an rbd suite at http://tracker.ceph.com/issues/20613#note-59 with one failure that passed on rerun.

Please review.

@dillaman

lgtm

@smithfarm smithfarm merged commit c049777 into ceph:jewel Sep 11, 2017

4 checks passed

Docs: build check OK - docs built
Details
Signed-off-by all commits in this PR are signed
Details
Unmodified Submodules submodules for project are unmodified
Details
make check make check succeeded
Details

@smithfarm smithfarm deleted the smithfarm:wip-20267-jewel branch Sep 11, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment