From 60ffbab63b6b767adf766c2fffdc0e19b6de62ca Mon Sep 17 00:00:00 2001 From: "James E. Blair" Date: Wed, 24 Feb 2016 10:44:13 -0800 Subject: [PATCH] Fix manual puppet run command docs Change-Id: I642ad27657806403431ff109afbea8b12f2ab6d9 --- doc/source/puppet.rst | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/doc/source/puppet.rst b/doc/source/puppet.rst index 2341dc1d3f..aa4e6f6cb2 100644 --- a/doc/source/puppet.rst +++ b/doc/source/puppet.rst @@ -113,12 +113,16 @@ creation of the master repos on the gerrit server. If an admin needs to run puppet by hand, it's a simple matter of either logging in to the server in question and running `puppet apply /opt/system-config/production/manifests/site.pp` or, on the -puppetmaster, running -`ansible-playbook --limit='$HOST;localhost' /opt/system-config/production/playbooks/remote_puppet_all.yaml` +puppetmaster, running: + +.. code-block:: bash + + ansible-playbook --limit='$HOST:localhost' /opt/system-config/production/playbooks/remote_puppet_else.yaml + as root, where `$HOST` is the host you want to run puppet on. If you are working with git, gerrit or afs servers, you'll want to replace -`remote_puppet_all.yaml` with the appropriate specific playbook. -The `;localhost` is important as some of the plays depend on performing a task +`remote_puppet_else.yaml` with the appropriate specific playbook. +The `:localhost` is important as some of the plays depend on performing a task on the localhost before continuing to the host in question, and without it in the limit section, the tasks for the host will have undefined values.