From 3fafd24a55fddbf23c358949230beeeb5cb67ffa Mon Sep 17 00:00:00 2001 From: Marc Gariepy Date: Tue, 7 Jun 2016 11:26:39 -0400 Subject: [PATCH] DOC - fix links in upgrade-playbooks * setup-infra-playbook * repo-server-pip-conf-removal * old-hostname-compatibility Change-Id: I4ec9de53b013b04983c7b41dc0ad14f42ba38e7b --- doc/source/upgrade-guide/upgrade-playbooks.rst | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/doc/source/upgrade-guide/upgrade-playbooks.rst b/doc/source/upgrade-guide/upgrade-playbooks.rst index 3ffe111bdd..41a4a88c4a 100644 --- a/doc/source/upgrade-guide/upgrade-playbooks.rst +++ b/doc/source/upgrade-guide/upgrade-playbooks.rst @@ -29,7 +29,7 @@ into the upgraded environment and generate appropriately. This adds only new secrets, such as those necessary for new services or new settings added to existing services. Values set previously are not changed. -.. _setup-infra-playbook: +.. _repo-server-pip-conf-removal: ``repo-server-pip-conf-removal.yml`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -38,7 +38,7 @@ The presence of ``pip.conf`` locks down all Python installations to packages on repo server. If ``pip.conf`` exists on the repo server, it creates a circular dependency, causing build failures. -.. _repo-server-pip-conf-removal: +.. _old-hostname-compatibility: ``old-hostname-compatibility.yml`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -49,7 +49,7 @@ in cases where the hostname is also the registered agent name. This playbook is only needed for upgrades of in-place upgrades of existing nodes or if a node is replaced or rebuilt it will be brought into the cluster using a compliant hostname. -.. _old-hostname-compatibility: +.. _setup-infra-playbook: ``setup-infrastructure.yml`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -81,8 +81,6 @@ upgrade RabbitMQ. The ``galera_upgrade`` variable tells the ``galera_server`` role to remove the current version of MariaDB and Galera and upgrade to the 10.x series. -.. _setup-infra-playbook: - -------------- .. include:: navigation.txt