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

group_vars: set strict host key checking to no for all hosts #41

Merged
merged 1 commit into from
Mar 8, 2024

Conversation

michael131468
Copy link
Owner

On some control nodes, ansible.cfg in the project space is not obeyed so try setting StrictHostChecking to no by default in the group_vars for all hosts.

This is needed because ssh'ing to newly instantiated managed nodes with random IPs will trigger typically an unknown host warning that blocks the playbook from completing automatically. With this, that warning is avoided and the playbook can complete.

On some control nodes, ansible.cfg in the project space is not obeyed
so try setting StrictHostChecking to no by default in the group_vars
for all hosts.

This is needed because ssh'ing to newly instantiated managed nodes with
random IPs will trigger typically an unknown host warning that blocks
the playbook from completing automatically. With this, that warning is
avoided and the playbook can complete.
@michael131468 michael131468 merged commit 3e5fec9 into main Mar 8, 2024
4 checks passed
@michael131468 michael131468 deleted the inventory_group_vars branch March 8, 2024 19:40
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.

1 participant