Jean-Philippe Evrard f1144a762c Use a venv with previous ansible version for upgrades ... When doing the role upgrade, we run every playbook with current's branch ansible. This is normal for the infrastructure bits (which are running on current branch), but not for the installation of the previous branch's role, which should use previous branch's environment. Depends-On: I7ebb045885dd645b820de2b7f75b46c755c015f6 Change-Id: Ied3168a4a2df385f8cba8f89b2efab208e639e55 Related-Bug: #1741471		2018-02-01 10:38:35 +00:00
..
group_vars	Ansible 2.1.1 update	2016-09-27 15:00:22 +00:00
host_vars	Fix role gate tests for Ansible 2.3	2017-04-19 15:51:34 -07:00
ansible-role-requirements.yml	Update upgrade role for Pike	2017-08-23 13:14:53 +01:00
benchmark-upgrade.yml	Add availability benchmark test to Cinder upgrade	2017-06-06 15:30:44 -04:00
inventory	Install lvm2 for cinder-volume LVM hosts	2017-06-19 14:23:12 +00:00
os_cinder-overrides.yml	Fix upgrade test	2018-01-23 13:15:21 +00:00
test-cinder-resources-results.yml	Add availability benchmark test to Cinder upgrade	2017-06-06 15:30:44 -04:00
test-cinder-resources-upgrade.yml	Fix upgrade test	2018-01-23 13:15:21 +00:00
test-cinder-upgrades.sh	Use a venv with previous ansible version for upgrades	2018-02-01 10:38:35 +00:00
test-install-previous-cinder.yml	Use a venv with previous ansible version for upgrades	2018-02-01 10:38:35 +00:00
test-upgrade.yml	Use a venv with previous ansible version for upgrades	2018-02-01 10:38:35 +00:00
test.yml	Split upgrade test into its own play	2017-01-20 16:36:21 +00:00
tests-repo-clone.sh	Update upgrade role for Queens from P	2017-10-17 18:28:22 +00:00