system-config/run_all.sh
Gregory Haynes b9945fccec Use ansible logging during puppet run_all.sh
When ansible-playbook outputs to stdout it does not include timestamps,
but ansible logging does.

Change-Id: Ifb63d34d1dcc7931d734d08dc31223b531d65aa2
2015-02-12 22:55:01 +00:00

44 lines
1.6 KiB
Bash
Executable File

#!/bin/bash
# Copyright 2014 Hewlett-Packard Development Company, L.P.
#
# Licensed under the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License. You may obtain
# a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations
# under the License.
# If updating the puppet system-config repo or installing puppet modules
# 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}
./install_modules.sh
# One must touch manifests/site.pp to trick puppet into re-loading modules
# some times
touch manifests/site.pp
# It's possible for connectivity to a server or manifest application to break
# for indeterminate periods of time, so the playbooks should be run without
# errexit
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
# 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
# Run everything else. We do not care if the other things worked
ansible-playbook /etc/ansible/playbooks/remote_puppet_else.yaml