It makes no sense to use become when you're connecting to a
host via the root remote_user. As such, we remove all uses of
'become: true' from the test plays with the exception of the
'test-prepare-keys.yml' playbook which uses a local connection
rather than a remote one and it therefore needs to use become.
We also transition all plays to use 'remote_user' which is the
correct parameter to replace 'user' (since ansible 1.4).
Finally, we switch the horizon nova service setup to its own
playbook using a local connection and the upstream keystone
modules.
Change-Id: I20517c22f07b1bb811a51d8c63741604360fe7f8
The current rabbitmq installation playbook assumes that there is
only a single rabbitmq container. While this works for most roles,
when more than one is desired in a test it requires a duplicated
playbook in the role which behaves differently.
This patch updates the playbook to make it more universal.
Change-Id: I372e0db39989ef412ab4301fcd5493efb48bdbe9
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
The swift role includes tasks that delegate to the physical host of
containers (localhost in gate tests). Since ansible_become was removed
from localhost's vars, set become in this play to fix tests that install
swift.
Also add the become option to all other plays to avoid this issue for
any other roles that may now or in the future delegate tasks to localhost.
Change-Id: I08cada62636a1a7a1e2c1b15e0052876437e24aa
Jesse Pretorius