Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use default ssh config when connecting to bastion #58

Merged
merged 1 commit into from
Feb 2, 2024

Conversation

LukeRepko
Copy link
Contributor

@LukeRepko LukeRepko commented Feb 1, 2024

During the infra-deploy playbook, ansible connects to the bastion or launcher node. It's best that this be done with the user's default ssh configuration in lieu of the generated one, otherwise connections to the bastion could fail.

Use ansible.builtin.ping to check liveness which is more thorough of a test. It will use the default ssh config, whereas wait_for ill only attempt a tcp connection, which may fail if a user has a default proxy configured as required in their environment.

@LukeRepko LukeRepko force-pushed the testenv branch 5 times, most recently from 0a9c8ae to bd04141 Compare February 1, 2024 20:11
@LukeRepko LukeRepko marked this pull request as draft February 1, 2024 22:50
@LukeRepko LukeRepko marked this pull request as ready for review February 2, 2024 00:13
@LukeRepko LukeRepko marked this pull request as draft February 2, 2024 00:15
@LukeRepko LukeRepko marked this pull request as ready for review February 2, 2024 00:40
During the infra-deploy playbook, ansible connects to the bastion or
launcher node. It's best that this be done with the user's default ssh
configuration in lieu of the generated one, otherwise connections to the
bastion could fail.

Use ansible.builtin.ping to check liveness which is more thorough of a
test. It will use the default ssh config, whereas wait_for will only
attempt a tcp connection, which may fail if a user has a default proxy
configured as required in their environment.
@cloudnull cloudnull merged commit c2ade09 into rackerlabs:main Feb 2, 2024
1 check passed
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