opendev/system-config
Code Issues Proposed changes

Use ansible logging during puppet run_all.sh

Browse Source 
When ansible-playbook outputs to stdout it does not include timestamps,
but ansible logging does.

Change-Id: Ifb63d34d1dcc7931d734d08dc31223b531d65aa2
This commit is contained in:
Gregory Haynes 2015-02-09 14:57:37 -08:00 committed by Elizabeth K. Joseph
parent 894b4c822d
commit b9945fccec
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
run_all.sh
View File

@ -18,6 +18,7 @@
# fails then abort the puppet run as we will not get the results we
# expect.
set -e
export ANSIBLE_LOG_PATH=/var/log/puppet_run_all.log
cd /opt/system-config/production
git fetch -a && git reset -q --hard @{u}
@ -34,9 +35,9 @@ set +e
# First run the git/gerrit sequence, since it's important that they all work
# together
ansible-playbook /etc/ansible/playbooks/remote_puppet_git.yaml >> /var/log/puppet_run_all.log 2>&1
ansible-playbook /etc/ansible/playbooks/remote_puppet_git.yaml
# Run AFS changes separately so we can make sure to only do one at a time
# (turns out quorum is nice to have)
ansible-playbook -f 1 /etc/ansible/playbooks/remote_puppet_afs.yaml >> /var/log/puppet_run_all.log 2>&1
ansible-playbook -f 1 /etc/ansible/playbooks/remote_puppet_afs.yaml
# Run everything else. We do not care if the other things worked
ansible-playbook /etc/ansible/playbooks/remote_puppet_else.yaml >> /var/log/puppet_run_all.log 2>&1
ansible-playbook /etc/ansible/playbooks/remote_puppet_else.yaml