doc/release-notes: ensure RBD users can blacklist prior to upgrade #17755
Conversation
doc/release-notes.rst
Outdated
| @@ -163,7 +163,8 @@ Major Changes from Kraken | |||
| * Specifying user authorization capabilities for RBD clients has been | |||
| simplified. The general syntax for using RBD capability profiles is | |||
| "mon 'profile rbd' osd 'profile rbd[-read-only][ pool={pool-name}[, ...]]'". | |||
| For more details see "User Management" in the documentation. | |||
| For more details see :doc:`rados/operations/user-management/` | |||
There was a problem hiding this comment.
rados/operation/user-management does not looks to be directory.
this is file user-management.rst
There was a problem hiding this comment.
The ":doc:" tag used throughout this file just links to the directories that are created when the .rst files are processed.
doc/release-notes.rst
Outdated
| @@ -417,6 +418,12 @@ Upgrade from Jewel or Kraken | |||
|
|
|||
| # ceph osd set noout | |||
|
|
|||
| #. Verify that all RBD client users have sufficient caps to blacklist | |||
| other client users. RBD client users with only ``"allow r"`` | |||
| monitor caps shold to be updated as follows:: | |||
|
@theanalyst Do we need to include this in the v12.2.1 release notes? @dillaman Can you correct the spelling of "should" as per @amitkumar50 review? |
|
I am out of the country presently -- if it can wait until next week, I'll fix it. Otherwise, can someone else open a new PR w/ the spelling fix? Thanks! |
|
@smithfarm since this is a doc only change lets just wait until we have a decision on whether we are going for a new build, if not I'll just merge in after we do a release |
Fixes: http://tracker.ceph.com/issues/21353 Signed-off-by: Jason Dillaman <dillaman@redhat.com>
|
spelling correction pushed |
Fixes: http://tracker.ceph.com/issues/21353
Signed-off-by: Jason Dillaman dillaman@redhat.com