openstack-zuul-jobs/tests/multinode_firewall_persistence_vars
Matthew Thode 3b03acabf4
add Gentoo jobs and vars and also fix install test
Based them on fedora-latest jobs

Depends-On: https://review.openstack.org/604677
Depends-On: https://review.openstack.org/604688
Change-Id: I45622ac18685b809a091edba2df96fc8040138a8
2018-09-25 20:57:29 -05:00
..
Debian.yaml Resolve Ansible variable precedence issue with include_vars 2018-03-02 11:18:22 -05:00
default.yaml Resolve Ansible variable precedence issue with include_vars 2018-03-02 11:18:22 -05:00
Gentoo.yaml add Gentoo jobs and vars and also fix install test 2018-09-25 20:57:29 -05:00
README.rst Resolve Ansible variable precedence issue with include_vars 2018-03-02 11:18:22 -05:00
RedHat.yaml Resolve Ansible variable precedence issue with include_vars 2018-03-02 11:18:22 -05:00
Suse.yaml Resolve Ansible variable precedence issue with include_vars 2018-03-02 11:18:22 -05:00
Ubuntu_trusty.yaml Resolve Ansible variable precedence issue with include_vars 2018-03-02 11:18:22 -05:00

multinode_firewall_persistence_vars

This directory is meant to contain distribution specific variables used in integration tests for the multinode_firewall_persistence role.

The behavior of the with_first_found lookup used with the include_vars module will make it search for the vars directory in the "usual" order of precedence which means if there is a vars directory inside the playbook directory, it will search there first.

This can result in one of two issues:

  1. If you try to prepend {{ role_path }} to workaround this issue with the variable file paths, Zuul will deny the lookup if you are running an untrusted playbook because the role was prepared in a trusted location and Ansible is trying to search outside the work root as a result.
  2. The variables included are the wrong ones -- the ones from playbooks/vars are loaded instead of path/to/<role>/vars

This is why this directory is called multinode_firewall_persistence_vars.