When targeting localhost with 'remote_user: root' and
using 'become: yes' we lose the environment variables
for the user running the playbook (eg: USER, HOME).
However, if we use 'connection: local' and 'become: yes'
together, it works properly.
To ensure these plays have the correct access to change
things on the host, we apply this change to them all.
We also ensure that 'become: no' is explicitly set on
any local connection plays to make the intent more
obvious. Finally, we also use 'yes' and 'no' uniformly.
Change-Id: I6e4607dd4aaffa0bfcda254103697bf9b28eca1a
Currently the find task only looks at one level deep
for repo folders, instead of the required three levels
deep.
Using the find module does not give us the ability to
set the depth level we want to do the find down to,
so we use a find command instead.
Change-Id: I0b218fe276292e13dbb40ab38c9a167025d16e45
Sometimes a test will result in a failure, but it
takes more time than necessary to find the failure
due to Ansible continuing to execute on other hosts
after removing one from the play execution.
This patch ensures that any error will result in
an immediate failure so that the fatal error is
easier to find.
Change-Id: I4e89bfdb1e48d0ac65f9fb8549e55a19ab773f9f
To avoid having to change each variable per release we can create a
single "test_branch" variable.
Additionally, when creating the "local-repo-packages.txt" constraints
file, we should use the "test_branch" variable to scope the constraints
file per release. This way upgrade jobs will continue to upgrade
correctly from the previous release's upstream project.
Change-Id: Ie9176fb561d0ef53051d1a39b5fb38dd30fb45bb
The tests repo will mount a directory set by the
"development_repo_directory" value into each container at the mount
point located at "development_repo_directory", both of which
default to "~/git/openstack".
Any directories found inside this directory will be used to generate a
"local-package-constraints.txt" pip install constraints file, which will
be used when installing pip packages. This will mean you can override
any pip package with the local repository, and doesn't limit this to
just existing service projects.
Change-Id: I774343234a25063eb320cac85ba696d908f0a416
Jonathan Rosser