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
mgr: print a more helpful error message for when users lack mgr ceph caps #15697
Conversation
26f7ed8
to
600bb7c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this really helps a lot 👍
👍 |
@@ -25,6 +25,15 @@ of ``ceph status``, which should now include a mgr status line:: | |||
|
|||
mgr active: $name | |||
|
|||
Client authentication | |||
--------------------- | |||
The manager is a new daemon which requires new CephX capabilities. If you upgrade |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should mention "new" here. When would it stop being new? In the next release? It would read fine with s/new//g here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The use of "you" and "your" can be removed, doesn't add anything specific to what authentication is trying to do. It would read like:
The manager is a daemon which requires CephX capabilities. When upgrading
a cluster from an old version of Ceph, or when using the default install/deploy
tools, the admin client should get this capability automatically. Using custom
tooling may get ``EACCES`` errors when invoking certain ceph cluster commands.
To fix that, add a "mgr allow *" stanza to the client's cephx capabilities by
… caps Add some brief documentation on updating their caps and link to it. Fixes: http://tracker.ceph.com/issues/20296 Signed-off-by: Greg Farnum <gfarnum@redhat.com>
600bb7c
to
6846f48
Compare
Here you go @alfredodeza |
No description provided.