Skip to content

feat: add retries to ssh_connection#2323

Merged
priteau merged 1 commit into
stackhpc/2025.1from
ssh-retries
May 22, 2026
Merged

feat: add retries to ssh_connection#2323
priteau merged 1 commit into
stackhpc/2025.1from
ssh-retries

Conversation

@jackhodgkiss
Copy link
Copy Markdown
Contributor

Some environments do not have a stable provisioning network and it is common to observe

Data could not be sent to remote host "10.144.0.174". Make sure this
host can be reached over ssh: ssh: connect to host 10.144.0.174
port 22: No route to host

By setting retries in ssh_connection these outages have not be observed.

@jackhodgkiss jackhodgkiss requested a review from a team as a code owner May 22, 2026 14:45
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a retry mechanism to the SSH connection settings in the Ansible configuration to improve resilience against transient network issues. The reviewer recommended adding a release note for this feature and including a descriptive comment for the new setting to maintain consistency within the configuration file.

Comment thread etc/kayobe/ansible.cfg
Comment thread etc/kayobe/ansible.cfg
Some environments do not have a stable provisioning network and it is
common to observe

```
Data could not be sent to remote host "10.144.0.174". Make sure this
host can be reached over ssh: ssh: connect to host 10.144.0.174
port 22: No route to host
```

By setting `retries` in `ssh_connection` these outages have not be
observed.

Signed-off-by: Jack Hodgkiss <jack@stackhpc.com>
@priteau priteau merged commit 52ecfeb into stackhpc/2025.1 May 22, 2026
25 of 26 checks passed
@priteau priteau deleted the ssh-retries branch May 22, 2026 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants