Skip to content

Conversation

@sd109
Copy link

@sd109 sd109 commented Oct 29, 2025

Since it uses a wait_for, any SSH config proxy jumps are not respected which means that in certain environments the task will never complete, even though future tasks which use SSH would still work correctly.

The Ansible issue referenced in the comment has apparently been resolved in Ansible 2.17.

Since it uses a wait_for, any SSH config proxy jumps are not
respected which means that in certain environments the task
will never complete, even though future tasks which use SSH
would still work correctly.
@sd109
Copy link
Author

sd109 commented Nov 6, 2025

Unfortunately, Ansible 2.17 requires Python 3.10 or later so in order to be able to remove this task and make it work in azimuth-config, we need to bump to Python 3.10 in this script and then update the minimum Ansible version in the azimuth- config requirements.txt.

@sd109
Copy link
Author

sd109 commented Nov 6, 2025

@sd109 sd109 requested a review from m-bull November 6, 2025 12:42
@sd109 sd109 marked this pull request as ready for review November 6, 2025 14:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants