Don't bail out in run_all.sh for ansible errors
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. Change-Id: Id4968de3ef8090faa8f97ae8bab29c282d595bbc
This commit is contained in:
parent
272d6ccc32
commit
bba9b3eef7
@ -27,6 +27,11 @@ git fetch -a && git reset -q --hard @{u}
|
|||||||
# some times
|
# some times
|
||||||
touch manifests/site.pp
|
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
|
# First run the git/gerrit sequence, since it's important that they all work
|
||||||
# together
|
# together
|
||||||
ansible-playbook /etc/ansible/remote_puppet_git.yaml >> /var/log/puppet_run_all.log 2>&1
|
ansible-playbook /etc/ansible/remote_puppet_git.yaml >> /var/log/puppet_run_all.log 2>&1
|
||||||
|
Loading…
x
Reference in New Issue
Block a user