You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
ASBishop
pushed a commit
to ASBishop/cbt
that referenced
this issue
Jun 10, 2016
+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
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.
The text was updated successfully, but these errors were encountered: