Export ANSIBLE_CONFIG so we can make sure it's used by Ansible

Ansible will read the configuration file found at ANSIBLE_CONFIG
automatically, regardless of location.
This ensures that scripts that run in the same context as
devstack-vm-gate-wrap.sh inherit from the same Ansible configuration.

This fixes the fact that network overlay playbook runs were missing
from the ARA report as they were running from "devstack-vm-gate.sh".

Change-Id: I53c30bc72477671f38b04f0331862e2bbfaed4d2
This commit is contained in:
David Moreau-Simard 2017-08-25 10:00:54 -04:00
parent a33308eb3b
commit c357066a9d
1 changed files with 2 additions and 1 deletions

View File

@ -482,6 +482,7 @@ virtualenv /tmp/ansible
devstack-tools==$DSTOOLS_VERSION ara
export ANSIBLE=/tmp/ansible/bin/ansible
export ANSIBLE_PLAYBOOK=/tmp/ansible/bin/ansible-playbook
export ANSIBLE_CONFIG="$WORKSPACE/ansible.cfg"
export DSCONF=/tmp/ansible/bin/dsconf
# Write inventory file with groupings
@ -496,7 +497,7 @@ for SUBNODE in $SUBNODES ; do
done
# Write ansible config file
cat > "$WORKSPACE/ansible.cfg" <<EOF
cat > $ANSIBLE_CONFIG <<EOF
[defaults]
callback_plugins = $WORKSPACE/devstack-gate/playbooks/plugins/callback:/tmp/ansible/lib/python2.7/site-packages/ara/plugins/callbacks
stdout_callback = devstack