doc/ceph-volume activate does not need a dmcrypt flag

Signed-off-by: Alfredo Deza <adeza@redhat.com>
(cherry picked from commit ac0c925c576868107e585ba458fbff956467bccb)

diff --git a/doc/ceph-volume/lvm/activate.rst b/doc/ceph-volume/lvm/activate.rst
index 66bed5a82e9b654f6d960e99dbae1476dced8f3c..6afd237832640c26490c2d067c884c8176a5b2d4 100644 (file)
--- a/doc/ceph-volume/lvm/activate.rst
+++ b/doc/ceph-volume/lvm/activate.rst
@@ -29,6 +29,13 @@ right OSD is being activated. It is entirely possible that a previous OSD with
 the same id exists and would end up activating the incorrect one.
 
 
+dmcrypt
+^^^^^^^
+If the OSD was prepared with dmcrypt by ceph-volume, there is no need to
+specify ``--dmcrypt`` on the command line again (that flag is not available for
+the ``activate`` subcommand). An encrypted OSD will be automatically detected.
+
+
 Discovery
 ---------
 With either existing OSDs or new ones being activated, a *discovery* process is