community.general/v1/ansible
Hugh Saunders 2e07567c16 Retry exec command via ssh_retry
This PR adds the option to retry failed ssh executions, if the failure
is caused by ssh itself, not the remote command. This can be helpful if
there are transient network issues. Retries are only implemented in the
openssh connection plugin and are disabled by default. Retries are
enabled by setting ssh_connection > retries to an integer greater
than 0.

Running a long series of playbooks, or a short playbook against a large
cluster may result in transient ssh failures, some examples logged
[here](https://trello.com/c/1yh6csEQ/13-ssh-errors).

Ansible should be able to retry an ssh connection in order to survive
transient failures.

Ansible marks a host as failed the first time it fails to contact it.
2015-05-18 14:22:52 -07:00
..
cache Making the switch to v2 2015-05-03 21:47:26 -05:00
callback_plugins Making the switch to v2 2015-05-03 21:47:26 -05:00
inventory Making the switch to v2 2015-05-03 21:47:26 -05:00
module_utils Making the switch to v2 2015-05-03 21:47:26 -05:00
modules Re-adding submodules after moving things around 2015-05-03 22:30:51 -05:00
playbook Making the switch to v2 2015-05-03 21:47:26 -05:00
runner Retry exec command via ssh_retry 2015-05-18 14:22:52 -07:00
utils moved module_doc_fragments to v2 2015-05-12 12:18:55 -04:00
__init__.py Making the switch to v2 2015-05-03 21:47:26 -05:00
callbacks.py Making the switch to v2 2015-05-03 21:47:26 -05:00
color.py Making the switch to v2 2015-05-03 21:47:26 -05:00
constants.py Making the switch to v2 2015-05-03 21:47:26 -05:00
errors.py Making the switch to v2 2015-05-03 21:47:26 -05:00
module_common.py made special treatment of certain filesystem for selinux configurable 2015-05-15 13:52:27 -04:00