Bump Ansible SSH ControlPersist param to 300s #2510
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We see the following error downstream [1], [2] indicates this error is caused by the SSH socket Ansible creates to multiplex connections fails.
Rather than handling the failure, Ansible fails the task. This is reportedly failing around 30% of the time on a very long running CI job.
300s was selected as it's used by the openstack-ansible project [3] [4]
Jira: https://issues.redhat.com/browse/OSPRH-10719
[1]
[2] ansible/ansible#78344 [3]
https://opendev.org/openstack/openstack-ansible/src/commit/32c6aa2cec1a2145e2c20a37df23f8b4e4b93e4c/scripts/openstack-ansible.rc#L52 [4] https://opendev.org/openstack/openstack-ansible/commit/cbdba67ad0b5a3e29db390c8e6b66721719184c0