a45afbeac5
There is an Ansible bug where if successive tasks are separated in time by the ssh controlpersist timeout Ansible will race ssh's updates to the connection causing the second task to fail with an rc of -13 [0]. Statistically we believe that the longer times between tasks are less likely. This means ssh controlpersist timeout values that are larger will be less likely to have ansible hit this bug. Increase the value from a default of 60s to 180s to take advantage of this probability. [0] https://github.com/ansible/ansible/issues/81777 Change-Id: Ic40730c3e0bd814e6a5c739e4415657594362032 |
||
---|---|---|
.. | ||
defaults | ||
files | ||
tasks | ||
templates | ||
README.rst |
Install and configure Ansible on a host via pip
This will install ansible into a virtualenv at
/usr/ansible-venv
Role Variables
A dictionary of configuration keys and their values for ARA's Ansible plugins.
Default configuration keys:
api_client: offline
(can behttp
for sending to remote API servers)api_server: http://127.0.0.1:8000
(has no effect when using offline)api_username: null
(if required, an API username)api_password: null
(if required, an API password)api_timeout: 30
(the timeout on http requests)For a list of available configuration options, see the ARA documentation