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

test: use librados API to retrieve config params #13076

Merged
merged 2 commits into from Jan 24, 2017

Conversation

Projects
None yet
3 participants
@dillaman
Contributor

dillaman commented Jan 24, 2017

The CephContext object is not ABI-stable, so it is necessary to
use the "conf_get" librados methods to safely retrieve a setting.

Fixes: http://tracker.ceph.com/issues/18617
Signed-off-by: Jason Dillaman dillaman@redhat.com

@trociny

LGTM

@trociny trociny self-assigned this Jan 24, 2017

@dillaman dillaman changed the title from test: use librados API to retrieve config params to [DNM] test: use librados API to retrieve config params Jan 24, 2017

dillaman added some commits Jan 24, 2017

test: use librados API to retrieve config params
The CephContext object is not ABI-stable, so it is necessary to
use the "conf_get" librados methods to safely retrieve a setting.

Fixes: http://tracker.ceph.com/issues/18617
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
librbd: improve debug logging for lock / watch state machines
Signed-off-by: Jason Dillaman <dillaman@redhat.com>

@dillaman dillaman changed the title from [DNM] test: use librados API to retrieve config params to test: use librados API to retrieve config params Jan 24, 2017

@dillaman

This comment has been minimized.

Contributor

dillaman commented Jan 24, 2017

@trociny trociny merged commit d4932a7 into ceph:master Jan 24, 2017

3 checks passed

Signed-off-by all commits in this PR are signed
Details
Unmodifed Submodules submodules for project are unmodified
Details
default Build finished.
Details

@dillaman dillaman deleted the dillaman:wip-18617 branch Jan 24, 2017

@smithfarm

This comment has been minimized.

Contributor

smithfarm commented Jan 25, 2017

@dillaman The second commit does not appear to be cherry-pickable to jewel. Can we omit it from the jewel backport entirely?

@dillaman

This comment has been minimized.

Contributor

dillaman commented Jan 25, 2017

@smithfarm I have a kraken version that should be cherry-pickable

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