group_vars: set strict host key checking to no for all hosts #41
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.
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.