Skip to content
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

radosbench fails if client cannot read admin keyring #105

Open
ASBishop opened this issue Jun 10, 2016 · 1 comment
Open

radosbench fails if client cannot read admin keyring #105

ASBishop opened this issue Jun 10, 2016 · 1 comment

Comments

@ASBishop
Copy link

The radosbench test uses the 'rados' tool, which requires the client admin key to access the cluster. The rados command will fail unless the user specified in the config file has read acess to the client admin keyring.

A workaround exists, and that is to set "cmd_path: 'sudo /usr/bin/rados'" in the test configuration. But this is cumbersome and breaks the ability to run the command under valgrind.

ASBishop pushed a commit to ASBishop/cbt that referenced this issue Jun 10, 2016
When running a radosbench test, execute the /usr/bin/rados command with sudo
in order to ensure the client can read the admin keyring.

Closes ceph#105
@bengland2
Copy link
Contributor

+1. Where else might this be happening? A casual search of the code shows a lot of candidates.

grep -r common.pdsh . | grep -v sudo

You don't need sudo for everything, but I thought you did need it for rbd, radosgw-admin, or ceph commands. I'll be sure to run everything as user cbt and make sure that it works that way. Error checking enablement will help point out problems with permissions.

ASBishop pushed a commit to ASBishop/cbt that referenced this issue Nov 3, 2016
When running a radosbench test, execute the /usr/bin/rados command with sudo
in order to ensure the client can read the admin keyring.

Closes ceph#105
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants