From e8cc72bad956a0746e12c4fe09d1295b99004c31 Mon Sep 17 00:00:00 2001 From: Luke Short Date: Tue, 15 Dec 2020 15:55:39 -0700 Subject: [PATCH] [troubleshoot-overcloud] Manual config-download Suggest that the Ansible content used for deployment be ran manually. Advice is provided on how to use it along with a link to existing documentation. Change-Id: Ia53fb7bf42a6f71d56474500f709f819749682ac Signed-off-by: Luke Short --- .../source/troubleshooting/troubleshooting-overcloud.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/deploy-guide/source/troubleshooting/troubleshooting-overcloud.rst b/deploy-guide/source/troubleshooting/troubleshooting-overcloud.rst index 569d356a..d371cb7f 100644 --- a/deploy-guide/source/troubleshooting/troubleshooting-overcloud.rst +++ b/deploy-guide/source/troubleshooting/troubleshooting-overcloud.rst @@ -289,3 +289,12 @@ Glance was an example, but all OpenStack services are supported. You can find th in the TripleO Heat Templates composable services. It is also possible to :ref:`toggle debug` for services after deployment. + +Manually Run the Deployment +^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +The deployment can be replicated by `manually running the config-download Ansible playbooks +`_. +This also allows the Ansible inventory, variables, playbooks, tasks, and more to be modified to +help narrow down issues. Consider using ``ansible-playbook --start-at-task`` to more quickly +troubleshooting an error.