Direct readers to the "Replacing an OSD" section in the cephadm
documentation, for cases in which the instructions in "Replacing an OSD"
in the RADOS documentation don't work.
https://tracker.ceph.com/issues/58401
Signed-off-by: Zac Dover <zac.dover@gmail.com>
(cherry picked from commit
7b8f75ebd7cd29faf2eec2fba1fefa17a390b92d)
This resets the initial state of the OSD and takes it off the removal queue.
+.. _cephadm-replacing-an-osd:
Replacing an OSD
----------------
Replacing an OSD
----------------
+.. note:: If the instructions in this section do not work for you, try the
+ instructions in the cephadm documentation ::ref:`cephadm-replacing-an-osd`.
+
When disks fail, or if an administrator wants to reprovision OSDs with a new
backend, for instance, for switching from FileStore to BlueStore, OSDs need to
be replaced. Unlike `Removing the OSD`_, replaced OSD's id and CRUSH map entry