doc: broken link on troubleshooting-mon page

Fixes: https://tracker.ceph.com/issues/37451
This fix involves adding :ref: labels to the add-or-rm-mons.rst
page. I also added :ref: labels for other headings within
add-or-rm-mons.rst (for future reference).

Signed-off-by: James McClune <jmcclune@mcclunetechnologies.net>
(cherry picked from commit ca05e456969a721631f5e9882c896cab76a4a3dc)

Conflicts:
	doc/rados/troubleshooting/troubleshooting-mon.rst
		Fixed the :ref: sentence and removed the _replace line.

diff --git a/doc/rados/operations/add-or-rm-mons.rst b/doc/rados/operations/add-or-rm-mons.rst
index 0cdc4313cc2586c9c14e36151d06523db805ce3d..20cba1bcabe9df59e99d52db2bae3fd10bcd7812 100644 (file)
--- a/doc/rados/operations/add-or-rm-mons.rst
+++ b/doc/rados/operations/add-or-rm-mons.rst
@@ -1,3 +1,5 @@
+.. _adding-and-removing-monitors:
+
 ==========================
  Adding/Removing Monitors
 ==========================
@@ -6,6 +8,8 @@ When you have a cluster up and running, you may add or remove monitors
 from the cluster at runtime. To bootstrap a monitor, see `Manual Deployment`_
 or `Monitor Bootstrap`_.
 
+.. _adding-monitors:
+
 Adding Monitors
 ===============
 
@@ -121,6 +125,7 @@ on ``mon.a``).
 
        ceph-mon -i {mon-id} --public-addr {ip:port}
 
+.. _removing-monitors:
 
 Removing Monitors
 =================

diff --git a/doc/rados/troubleshooting/troubleshooting-mon.rst b/doc/rados/troubleshooting/troubleshooting-mon.rst
index 89fb94c32f998bd57bb4a30c38ee565a88c374e8..642b2e07bfd18f0584e099a5d8cc4d86a5b9d9cd 100644 (file)
--- a/doc/rados/troubleshooting/troubleshooting-mon.rst
+++ b/doc/rados/troubleshooting/troubleshooting-mon.rst
@@ -402,8 +402,8 @@ or::
 Recovery using healthy monitor(s)
 ---------------------------------
 
-If there is any survivers, we can always `replace`_ the corrupted one with a
-new one. And after booting up, the new joiner will sync up with a healthy
+If there are any survivors, we can always :ref:`replace <adding-and-removing-monitors>` the corrupted one with a
+new one. After booting up, the new joiner will sync up with a healthy
 peer, and once it is fully sync'ed, it will be able to serve the clients.
 
 Recovery using OSDs
@@ -563,5 +563,4 @@ Finally, you should reach out to us on the mailing lists, on IRC or file
 a new issue on the `tracker`_.
 
 .. _cluster map: ../../architecture#cluster-map
-.. _replace: ../operation/add-or-rm-mons
 .. _tracker: http://tracker.ceph.com/projects/ceph/issues/new