Removed --dry-run from OSD replace command

SUSE · Jan 31, 2024 · d182c2a · d182c2a
1 parent afb4c78
commit d182c2a
Showing 1 changed file with 22 additions and 27 deletions.
diff --git a/xml/admin_saltcluster.xml b/xml/admin_saltcluster.xml
@@ -1176,33 +1176,28 @@ OSD_ID  HOST         STATE                    PG_COUNT  REPLACE  FORCE  STARTED_
     For example:
    </para>
 <screen>&prompt.cephuser;ceph orch osd rm 4 --replace</screen>
-   <para>
-    Replacing an OSD is identical to removing an OSD (see
-    <xref linkend="removing-node-osds"/> for more details) with the exception
-    that the OSD is not permanently removed from the CRUSH hierarchy and is
-    assigned a <literal>destroyed</literal> flag instead.
-   </para>
-   <para>
-    The <literal>destroyed</literal> flag is used to determined OSD IDs that
-    will be reused during the next OSD deployment. Newly added disks that match
-    the &drvgrps; specification (see <xref linkend="drive-groups"/> for more
-    details) will be assigned OSD IDs of their replaced counterpart.
-   </para>
-   <tip>
-    <para>
-     Appending the <option>--dry-run</option> option will not execute the
-     actual replacement, but will preview the steps that would normally happen.
-    </para>
-   </tip>
-   <note>
-    <para>
-     In the case of replacing an OSD after a failure, we highly recommend
-     triggering a deep scrub of the placement groups. See
-     <xref linkend="scrubbing-pgs"/> for more details.
-    </para>
-    <para>
-     Run the following command to initiate a deep scrub:
-    </para>
+      <para>
+        Replacing an OSD is identical to removing an OSD (see
+        <xref linkend="removing-node-osds"/> for more details) with the
+        exception that the OSD is not permanently removed from the CRUSH
+        hierarchy and is assigned a <literal>destroyed</literal> flag instead.
+      </para>
+      <para>
+        The <literal>destroyed</literal> flag is used to determined OSD IDs
+        that will be reused during the next OSD deployment. Newly added disks
+        that match the &drvgrps; specification (see
+        <xref linkend="drive-groups"/> for more details) will be assigned OSD
+        IDs of their replaced counterpart.
+      </para>
+      <note>
+        <para>
+          In the case of replacing an OSD after a failure, we highly recommend
+          triggering a deep scrub of the placement groups. See
+          <xref linkend="scrubbing-pgs"/> for more details.
+        </para>
+        <para>
+          Run the following command to initiate a deep scrub:
+        </para>
 <screen>&prompt.cephuser;ceph osd deep-scrub osd.<replaceable>OSD_NUMBER</replaceable></screen>
    </note>
    <important>